Re: [boost] Problems building --v2 (x86_64)

From: David Abrahams (dave_at_[hidden])
Date: 2004-09-07 12:56:08

Vladimir Prus <ghost_at_[hidden]> writes:

> Hi Neal,
>> PYTHON_ROOT=/usr PYTHON_VERSION=2.3 PYTHON_LIB_PATH=/usr/lib64/python2.3
>> bjam --v2
>
> Please direct Boost.Build question to the jamboost mailing list.
>
>> ...patience...
>> ...found 986 targets...
>> ...updating 113 targets...
>> MkDir1 bin.v2
>> MkDir1 bin.v2/libs
>> MkDir1 bin.v2/libs/test
>> MkDir1 bin.v2/libs/test/build
>> MkDir1 bin.v2/libs/test/build/gcc
>> MkDir1 bin.v2/libs/test/build/gcc/debug
>> gcc.compile.c++ bin.v2/libs/test/build/gcc/debug/execution_monitor.o
>> gcc.compile.c++ bin.v2/libs/test/build/gcc/debug/cpp_main.o
>> gcc.link.dll bin.v2/libs/test/build/gcc/debug/boost_prg_exec_monitor.so
>> /usr/bin/ld: bin.v2/libs/test/build/gcc/debug/execution_monitor.o:
>> relocation R_X86_64_32 can not be used when making a shared object;
>> recompile with -fPIC
>
> In turns out that on X86_64 and on some "other platforms", shared libraries 
> must be build with -fPIC, for uknown reasons. While they can be build without 
> -fPIC on X86_32, that's also "nonstandard". So, I've changed V2 to always 
> pass -fPIC.

I hope you're only doing that for shared libraries.

-- 
Dave Abrahams
Boost Consulting
http://www.boost-consulting.com