|
From: | f.michal |
Subject: | Re: [Openexr-devel] pyilmbase 2.2.0 build - boost::python test program failure |
Date: | Mon, 10 Oct 2016 15:38:39 +0200 |
User-agent: | Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 |
I just realised I replied directly to
Peter instead to the list. So again, here's my post with solution:
I turned out I needed to rebuild python with --enable-shared configure path. Otherwise I was missing some default system libs. Example from config.log: configure:16122: checking for boost::python configure:16168: g++ -o conftest -g -O2 -I/home/mfratczak/dev/projs/python/Python-2.7.12_gcc482/install/include/python2.7 -g -O2 -I/home/mfratczak/dev/projs/python/Python-2.7.12_gcc482/install/include/python2.7 -L/home/mfratczak/dev/libs/OpenEXR/2.2.0/install3/lib -L/usr/local/lib -L/home/mfratczak/dev/libs/boost/boost_1_61_0/stage/lib -L/home/mfratczak/dev/projs/python/Python-2.7.12_gcc482/install/lib -L/home/mfratczak/dev/libs/OpenEXR/2.2.0/install3/lib -L/usr/local/lib -L/home/mfratczak/dev/libs/boost/boost_1_61_0/stage/lib -L/home/mfratczak/dev/projs/python/Python-2.7.12_gcc482/install/lib conftest.cpp -ldl -lpthread -lpython2.7 -lboost_python -ldl -lpthread -lpython2.7 >&5 /home/mfratczak/dev/projs/python/Python-2.7.12_gcc482/install/lib/libpython2.7.a(posixmodule.o): In function `posix_tmpnam': /home/mfratczak/dev/projs/python/Python-2.7.12_gcc482/./Modules/posixmodule.c:7631: warning: the use of `tmpnam_r' is dangerous, better use `mkstemp' /home/mfratczak/dev/projs/python/Python-2.7.12_gcc482/install/lib/libpython2.7.a(posixmodule.o): In function `posix_tempnam': /home/mfratczak/dev/projs/python/Python-2.7.12_gcc482/./Modules/posixmodule.c:7578: warning: the use of `tempnam' is dangerous, better use `mkstemp' /opt/rh/devtoolset-2/root/usr/libexec/gcc/x86_64-redhat-linux/4.8.2/ld: /home/mfratczak/dev/projs/python/Python-2.7.12_gcc482/install/lib/libpython2.7.a(posixmodule.o): undefined reference to symbol 'forkpty@@GLIBC_2.2.5' /opt/rh/devtoolset-2/root/usr/libexec/gcc/x86_64-redhat-linux/4.8.2/ld: note: 'forkpty@@GLIBC_2.2.5' is defined in DSO /lib64/libutil.so.1 so try adding it to the linker command line /lib64/libutil.so.1: could not read symbols: Invalid operation collect2: error: ld returned 1 exit status configure:16172: $? = 1 configure: program exited with status 1 So, all seems to be OK now. Are there any other python flags relevant for us (maya/exr users)? I think I saw some other, possibly enabling utf support AFAIR... thanks! -michal W dniu 2016-10-06 o 02:36, Peter Hillman pisze:
|
[Prev in Thread] | Current Thread | [Next in Thread] |