13 Dec 2013 13 Dec '13
On 13.12.2013 18:46, David Jones wrote:
Correction. Of course LD_LIBRARY_PATH isn't seen by the compiler. It only applies at run time. How embarrasing:) This isn't the first time I've been bitten by that.
I don't mind doing that with manual builds, but what about with pip? Is there a way to avoid explicitly setting the library path every time you call pip, when using a custom python install?
why are you actually doing this?
the easiest way to get 32 bit binaries for any program is simply using a 32 bit chroot to build them. This is trivial to do on a debian based systems:
pbuilder-dist i386 unstable create pbuilder-dist i386 unstable login # install dependencies and build as usual