Peter Jones wrote:
Hey, remember back when Rene Rivera said:
The gcc toolset is already adding the -pthread option when linking multi-threaded variants (lines 143-145). Are you saying you need to use -pthread even when linking single-threaded variants?
This is what "bjam -sTOOLS=gcc -sBUILD=release" produces without my change to gcc-tools.jam:
Which builds the release single-threaded variants.
gcc-Link-action bin/boost/libs/filesystem/build/libboost_filesystem.so/gcc/release/shared-linkable-true/libboost_filesystem-gcc-1_31.so bin/boost/libs/filesystem/build/libboost_filesystem.so/gcc/release/shared-linkable-true/libboost_filesystem-gcc-1_31.imp ld: 0711-317 ERROR: Undefined symbol: .pthread_mutex_lock ld: 0711-317 ERROR: Undefined symbol: .pthread_mutex_unlock ld: 0711-317 ERROR: Undefined symbol: .pthread_mutex_init ld: 0711-317 ERROR: Undefined symbol: .pthread_mutex_destroy
Is there a way to tell who is referencing those symbols? As it might not be Boost code but other runtime code. -- Something to try would be to compile an empty *.so. That is compile an empty source file and try doing a "-shared" link. If you get thread errors with an empty shared library, then the problem is that the GCC+AIX runtimes require threading. And I'll fix that on the toolset, and post a patch ;-) -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com - 102708583/icq