From: Jos Hickson (jos.hickson_at_[hidden])
Date: 2007-06-29 06:59:19
The release variant uses <optimization>speed (setting the -O3 flag for
GCC) and <inlining>full but that results in binaries that seg fault.
This appears to have something to do with the full inlining. Using
conditions in our project Jamfiles it is easy enough to get release to
use <inlining>on but unfortunately the -O3 flag also sets full
inlining on so we would rather use -O2.
For the moment I have altered the definition of <optimization>speed in
gcc.jam to use -O2 instead of -O3 but I would much rather override the
definition in our own Jamfiles, Jamroot or site-config.jam. Is there
any way to do that? I've tried putting
flags gcc.compile OPTIONS <optimization>speed : -O2 ;
in our site-config.jam but I get the error
error: Module site-config attempted to set flags for module gcc.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk