Nevermind, got the python build problem solved.
Apparently, I have to specify CFLAGS=-m32 instead of OPT=-m32 on my
platform.
Now I have a working 32bit installation of pyhton under /opt/pym32/
I now created a file named user-config.jam with the following content:
using python : : /opt/pym32/bin
I also tried python 2.6.6 now, getting the same result.
The core dump yields this stack trace:
Core was generated by `./python -c import sys; print sys.maxint'.
Program terminated with signal 11, Segmentation fault.
#0 pmerge (type=0x0) at Objects/typeobject.c:1462
1462to_merge_size = PyL
On 10/05/2010 11:07 AM, Philipp Münzel wrote:
Hi Charles,
thanks for the fast answer!
So I downloaded python 2.7 source and did:
OPT=-m32 LDFLAGS=-m32 ./configure --prefix=/opt/pym32
make
Unfortunately, the build fails:
/bin/sh: line 1: 23704 Segmentation fault CC='gcc -pthread'
LDSHARE
Hi Charles,
thanks for the fast answer!
So I downloaded python 2.7 source and did:
OPT=-m32 LDFLAGS=-m32 ./configure --prefix=/opt/pym32
make
Unfortunately, the build fails:
/bin/sh: line 1: 23704 Segmentation fault CC='gcc -pthread'
LDSHARED='gcc -pthread -shared' LDFLAGS='-m32' OPT='-DND
You need to compile boost python with a 32 bit version of python. The
version bjam is finding is 64 bit. If you have a 32 bit python
somewhere you need to tell bjam where to find the right headers. See
this page
http://www.boost.org/doc/libs/1_44_0/libs/python/doc/building.html#configuring-boos
Hi everyone,
I'm trying to build a Boost.Python 32bit static library on a 64bit Linux
(Suse 11.3).
Of course, I have the respective python-devel and python32 packages for
my platform installed.
I build my minimal work environment of boost-thread, -system and -python
with this command:
sudo ./bj
