Building Python with non-traditional paths
Is there a clean way to build Python under a non-traditional path,
linking with other software that is under non-traditional paths, on
I maintain a build of Python  that is part of a self-contained
bundle of software  to run bcfg2 .
The major problem I am having is getting the build to link to the
openssl libraries, which are installed under /usr/local/lib/bcfg2/lib;
I tried (on GNU/Linux):
but that didn't work. The only thing I could do to get it to work
(sometimes) was to edit the setup.py file directly before the
../configure; make; make install like this:
cat setup.py \
| sed s:\/usr\/local\/:\/usr\/local\/lib\/bcfg2\/:g \
mv setup.py.bcfg2 setup.py
However that is rather ugly, and modifies the source which I'd rather
not do. Is there a better/cleaner way?
 Complete build spec for Python for Bcfg2
 Bcfg2 Encap Packages - Overview
 Bcfg2 - Provides a declarative interface to system configuration
|All times are GMT. The time now is 04:36 PM.|
Powered by vBulletin®. Copyright ©2000 - 2014, vBulletin Solutions, Inc.
SEO by vBSEO ©2010, Crawlability, Inc.