[Numpy-discussion] building 32 bit numpy on 64 bit linux

David Jones david.jones74 at gmail.com
Mon Dec 16 17:25:32 EST 2013

On 12/13/13 13:48, Julian Taylor wrote:
> 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
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at scipy.org
> http://mail.scipy.org/mailman/listinfo/numpy-discussion

Just a follow-up. After building python with the -rpath linker flag set, 
I can install numpy using pip without having to specify the library path 

CC=gcc-32 LDSHARED=ld-32 pip install numpy

However, this doesn't work for building numpy directly. So it seems that 
pip is doing some clever magic here.

In addition, pip perpetuates the -rpath value from python when building 
packages, so they have the correct run-time path to libpython.

More information about the NumPy-Discussion mailing list