Re: [Boost-testing] Problem building bjam for xlc on linuxppc

Subject: Re: [Boost-testing] Problem building bjam for xlc on linuxppc
From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2008-11-25 23:29:42

Chris Cambly wrote:
> If we try to build bjam on linux using xlC the build fails because of an 
> invalid linker option.  The file tools/jam/src/build.jam has the following:
> 
> ## IBM VisualAge C++
> toolset vacpp xlc : "-o " : -D
>     :
>     [ opt --release : -s -O3 -qstrict -qinline ]
>     [ opt --debug : -g -qNOOPTimize -qnoinline -pg ]
>     -I$(--python-include) -I$(--extra-include)
>     : -L$(--python-lib[1]) -l$(--python-lib[2]) -bmaxdata:0x40000000 ;
> 
> The -bmaxdata linker option is only valid on AIX.  If I am building with 
> xlC on Linux that linker option should not be specified.
> 
> I can do something like:
> 
> ## IBM VisualAge C++
> {
> local linkopt = ; if $(OS) = AIX { linkopt = -bmaxdata:0x40000000 ; }
> toolset vacpp xlc : "-o " : -D
>     :
>     [ opt --release : -s -O3 -qstrict -qinline ]
>     [ opt --debug : -g -qNOOPTimize -qnoinline -pg ]
>     -I$(--python-include) -I$(--extra-include)
>     : -L$(--python-lib[1]) -l$(--python-lib[2]) $(linkopt) ;
> }
> 
> Is this ok or is there a better way to do this?  Sorry for asking, but I 
> have not been following the tools changes as closely as I should.

I don't think you missed anything by not paying attention, as that bit 
of code hasn't changed in a long time. And other than using the uname 
var instead of OS the above seems like the likeliest solution.

-- 
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software.com
-- rrivera/acm.org (msn) - grafik/redshift-software.com
-- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail