Subject: Re: [Boost-build] changing file output suffixes
From: Vladimir Prus (ghost_at_[hidden])
Date: 2009-06-30 11:43:52
On Tuesday 30 June 2009 McLemon, Sean wrote:
> > GCC uses 'eabi' and 'elf' on some targets to mean bare metal. We can
> > either
> > use those, in indeed introduce 'bare' as target-os.
> I think "elf" makes more sense. If it's possible that would be a useful
> addition for us.
I've added 'elf' as a new value of target-os.
> > I'm confused. Are the object files created? (Which would suggest that
> > error
> > message comes from compiler) Or the compilation fails, while the
> > /c/analog/tools5.0_andromeda/ccblkfn file exists? I'd suggest you try
> > to
> > specify the path using Windows paths and see what happens.
> Quite embarassingly I think we can chalk this one up to "User error" :)
> When I changed the "using bfin: ..." line in my user-config.jam to the
> below (i.e. using windows paths) I no longer get the message (I do get a
> wonderful compiler crash, but that is due to using an non-mature
> development compiler):
> using bfin : 220.127.116.11 : c:/analog/tools5.0_andromeda/ccblkfn ;
Good to know it's not Boost.Build fault :-). Should you need any further
tweaks from Boost.Build, let us know. Hopefully support for your compiler
can be added to SVN in near future.
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