Peter Dimov wrote:
It seems that to fix the problem we need to set v9 as default in Boost.Build. I admit that I have no idea how to do that. Searching *.jam for -mcpu turned up nothing. The instruction-set feature doesn't seem to be used by gcc.jam. (The CVS only has Boost.Build v2 now; it could've worked with v1.)
I can add the architecture and cpu options into BBv2, from BBv1. But we probably don't want to do that in the 1.34 branch as I don't think we want the chance of upsetting testing. Is that reasonable, or is this an urgent problem? -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo