As a follow up, here's an explanation of how to do this without pip or
virtualenv. To do it with virtualenv, just place the wrapper scripts in
your virtualenv's bin directory:
To build python:
Install python build dependencies (on Centos 6). Make sure to get the i686
packages:
tk-devel, tcl-devel
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 wi
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 wi
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
On 12/13/13 11:24, Charles G. Waldman wrote:
this might work:
CC="gcc -m32" LDSHARED="gcc -m32" FF="gfortran -m32" linux32 python
setup.py build
> Compiler flags can't be added to CC, they should be in CFLAGS. (and
> ld flags go into LDFLAGS). Otherwise you are saying to use
On 12/13/13 11:24, Charles G. Waldman wrote:
this might work:
CC="gcc -m32" LDSHARED="gcc -m32" FF="gfortran -m32" linux32 python
setup.py build
> Compiler flags can't be added to CC, they should be in CFLAGS. (and
> ld flags go into LDFLAGS). Otherwise you are saying to use
>>> this might work:
>>>
>>> CC="gcc -m32" LDSHARED="gcc -m32" FF="gfortran -m32" linux32 python
>>> setup.py build
Compiler flags can't be added to CC, they should be in CFLAGS. (and
ld flags go into LDFLAGS). Otherwise you are saying to use a program
called "gcc -m32" (with a space in the name
On 12/12/13 16:35, Julian Taylor wrote:
> On 12.12.2013 20:40, David Jones wrote:
>> On 12/12/13 15:54, Julian Taylor wrote:
>>> On 12.12.2013 19:58, David Jones wrote:
I'm trying to compile 32-bit numpy on a 64 bit Centos 6 system, but fails
with the message:
"Broken toolchai
On 12/12/13 16:35, Julian Taylor wrote:
> On 12.12.2013 20:40, David Jones wrote:
>> On 12/12/13 15:54, Julian Taylor wrote:
>>> On 12.12.2013 19:58, David Jones wrote:
I'm trying to compile 32-bit numpy on a 64 bit Centos 6 system, but fails
with the message:
"Broken toolchain
On 12/12/13 16:35, Julian Taylor wrote:
> On 12.12.2013 20:40, David Jones wrote:
>> On 12/12/13 15:54, Julian Taylor wrote:
>>> On 12.12.2013 19:58, David Jones wrote:
I'm trying to compile 32-bit numpy on a 64 bit Centos 6 system, but fails
with the message:
"Broken toolchai
On 12.12.2013 20:40, David Jones wrote:
> On 12/12/13 15:54, Julian Taylor wrote:
>> On 12.12.2013 19:58, David Jones wrote:
>>> I'm trying to compile 32-bit numpy on a 64 bit Centos 6 system, but fails
>>> with the message:
>>>
>>> "Broken toolchain: cannot link a simple C program"
>>>
...
>>>
>>
On 12/12/13 15:54, Julian Taylor wrote:
> On 12.12.2013 19:58, David Jones wrote:
>> I'm trying to compile 32-bit numpy on a 64 bit Centos 6 system, but fails
>> with the message:
>>
>> "Broken toolchain: cannot link a simple C program"
>>
>> It get's the compile flags right, but not the linker:
>
On 12.12.2013 19:58, David Jones wrote:
> I'm trying to compile 32-bit numpy on a 64 bit Centos 6 system, but fails
> with the message:
>
> "Broken toolchain: cannot link a simple C program"
>
> It get's the compile flags right, but not the linker:
>
> C compiler: gcc -pthread -fno-strict-alias
I'm trying to compile 32-bit numpy on a 64 bit Centos 6 system, but fails with
the message:
"Broken toolchain: cannot link a simple C program"
It get's the compile flags right, but not the linker:
C compiler: gcc -pthread -fno-strict-aliasing -g -O2 -m32 -DNDEBUG -g -fwrapv
-O3 -Wall -Wstrict-
14 matches
Mail list logo