Re: [Boost-build] GCC/x86_64 toolset(?) problems

From: David Abrahams (dave_at_[hidden])
Date: 2008-08-27 21:51:00

on Wed Aug 27 2008, Juergen Hunold <juergen.hunold-AT-ivembh.de> wrote:

> On Wednesday 27 August 2008 21:53:53 David Abrahams wrote:
>> Hi,
>>
>> I've been trying to run the Boost 1.35.0 tests with GCC on Suse Linux
>> Enterprise Server 10/AMD64, and there are some failures that indicate we
>> got something wrong somewhere. 
>
> Wow. Thats old ;-))
>
>> /usr/lib64/gcc/x86_64-suse-linux/4.1.0/../../../../x86_64-suse-linux/bin/ld
>>: /zorak/sles/build/boost/bin.v2/libs/statechart/test/gcc-4.1.0/release/
>> link-static/LibTestNormalLibTuTest.o:
>>     relocation R_X86_64_32 against `a local symbol' can not be used when
>>     making a shared object; recompile with -fPIC
>>
>> I assume that there's something wrong with what Boost.Build is doing
>> here, but I'm at a loss as to how it might be fixed.
>
> Well, x86_64 gcc targets sometimes requires -fPIC even for static builds. So 
> add <cxxflags>-fPIC to your user config jam or the Jamfile for Boost.StateChart. 
> And do a full (!) recompile.

-a cxxflags=-fPIC on the command line doesn't work.  I tried that already.  

> This has been fixed on trunk and 1.36.0. Note that command line arguments will 
> not work due to a BB bug.

Ooooooh.  That explains a lot, thanks.

> There should be some mails on the list archives about this issue, too.

OK, I'd really like to apply the necessary patches.  However, the only
one I can identify is:

  http://svn.boost.org/trac/boost/changeset/47719

Can you help?

Thanks,

-- 
Dave Abrahams
BoostPro Computing
http://www.boostpro.com