On Jun 3, 2007, at 9:09 AM, Chris Fairles wrote:
Error #1:
Building with:
./tools/jam/src/bin.linux/bjam -d+2 -sICU_PATH=/usr variant=release threading=multi --layout=system --user-config=user-config.jam --with-date_time --with-filesystem --with-function_types --with-iostreams --with-mpi --with-program_options --with-python --with-serialization --with-signals --with-system --with-thread --with-test
I obtained the following linker error.
/usr/bin/ld: bin.v2/libs/mpi/build/gcc-4.1.1/release/link-static/ threading-multi/collectives.o: relocation R_X86_64_32 against `__dso_handle' can not be used when making a shared object; recompile with -fPIC
Solved by adding using gcc : : : <cxxflags>-fPIC ; to user-config.jam
Okay, thanks!
Error #2:
./tools/jam/src/bin.linux/bjam -d+2 -sICU_PATH=/usr variant=release threading=multi --layout=system --user-config=user-config.jam --prefix=/home/cfairles/usr --exec-prefix=/home/cfairles/usr --libdir=/home/cfairles/usr/lib64 --includedir=/home/cfairles/usr/include --with-date_time --with-filesystem --with-function_types --with-iostreams --with-mpi --with-program_options --with-python --with-serialization --with-signals --with-system --with-thread --with-test install /home/cfairles/repos/boost/tools/build/v2/build/virtual-target.jam: 996: in virtual-target.register-actual-name from module virtual-target error: Duplicate name of actual target:
mpi.so error: previous virtual target { common%common.copy-mpi.so.PYTHON_EXTENSION { [snip big error] Not all Boost libraries built properly.
Haven't found a workaround yet.
This is a know (but still unsolved!) problem with BBv2 and Boost.MPI's Python module. If you turn off Python support in user- config.jam, the rest of Boost.MPI should build and install correctly. I'm trying to find a real workaround, still. - Doug