Building and testing filesystem library on AIX

I'm trying to build and test Boost on AIX 5.3, with gcc 3.3.2, but not getting very far. I'm focusing on the filesystem library, using the following build command: $ bjam "-sTOOLS=gcc" "-sBUILD=release debug <threading>single/multi <runtime-link>static/dynamic <linkflags>-pthread" --without-python --with-filesystem stage Without "<linkflags>-pthread", it fails with errors like "Undefined symbol: .pthread_mutex_lock". So, this command seems to work okay, although I do get the following linker warnings for all four .so links: ld: 0711-224 WARNING: Duplicate symbol: _GLOBAL__F_thread_creds_t ld: 0711-224 WARNING: Duplicate symbol: thread_creds_t ld: 0711-224 WARNING: Duplicate symbol: ._GLOBAL__I_thread_creds_t ld: 0711-224 WARNING: Duplicate symbol: ._GLOBAL__D_thread_creds_t ld: 0711-224 WARNING: Duplicate symbol: _GLOBAL__I_thread_creds_t ld: 0711-224 WARNING: Duplicate symbol: _GLOBAL__D_thread_creds_t Then I want to verify the build, so I cd down into libs/filesystem/test, and try to run the test there by executing the following (the <linkflags>-pthread still seems to be required): $ bjam "-sBUILD=<linkflags>-pthread" The first problem I run into is this: ld: 0706-006 Cannot find or open library file: -l boost_filesystem-gcc-d-1_33_1 In the only "-L" directory listed in the g++ command line printed out after that ("../../../bin/boost/libs/filesystem/build/libboost_filesystem.so/gcc/debug/shared-linkable-true"), there is a libboost_filesystem-gcc-d-1_33_1.so, but no libboost_filesystem-gcc-d-1_33_1.a. So I manually copy the built libboost_filesystem-gcc-d-1_33_1.a from "../../../stage/lib", and try the same bjam command again. This time, the build part seems to work, though it gives the same linker warnings shown above for 2 of the 7 links ("../../../bin/boost/libs/filesystem/test/path_test_dll.test/gcc/debug/path_test_dll" and "../../../bin/boost/libs/filesystem/test/operations_test_dll.test/gcc/debug/operations_test_dll"). Then it tries to run the first test, but immediately crashes: execute-test ../../../bin/boost/libs/filesystem/test/path_test.test/gcc/debug/path_test.run ====== BEGIN OUTPUT ====== Platform is POSIX /data2/cgrayson/boost_1_33_1/boost/test/minimal.hpp(122): exception "signal: SIGABRT (application abort requested)" caught in function: 'int main(int, char**)' **** Testing aborted. **** 1 error detected EXIT STATUS: 201 ====== END OUTPUT ====== Any help would be greatly appreciated - thanks. Chris Grayson Database-Brothers, Inc. Austin, TX

<chris.grayson@database-brothers.com> wrote in message news:20060509141357.308a11decd0321d080adbf459a9b6112.c28baef6f7.wbe@email.secureserver.net...
I'm trying to build and test Boost on AIX 5.3, with gcc 3.3.2, but not getting very far. I'm focusing on the filesystem library, using the following build command:
$ bjam "-sTOOLS=gcc" "-sBUILD=release debug <threading>single/multi <runtime-link>static/dynamic <linkflags>-pthread" --without-python --with-filesystem stage
Without "<linkflags>-pthread", it fails with errors like "Undefined symbol: .pthread_mutex_lock".
Boost.Filesystem doesn't directly do any multi-threading, but it does use shared_ptr. Are the shared_ptr tests working for you? If not, you need to resolve those problems before trying Boost.Filesystem.
...
Then it tries to run the first test, but immediately crashes:
execute-test ../../../bin/boost/libs/filesystem/test/path_test.test/gcc/debug/path_test.run ====== BEGIN OUTPUT ====== Platform is POSIX /data2/cgrayson/boost_1_33_1/boost/test/minimal.hpp(122): exception "signal: SIGABRT (application abort requested)" caught in function: 'int main(int, char**)'
**** Testing aborted. **** 1 error detected
EXIT STATUS: 201 ====== END OUTPUT ======
Any chance of getting a call stack trace at time of abort? --Beman
participants (2)
-
Beman Dawes
-
chris.grayson@database-brothers.com