> 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'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 : 8.0.7.1 : c:/analog/tools5.0_andromeda/ccblkfn ;
Thanks again for your help, Volodya
- Sean
_______________________________________________
Unsubscribe & other changes:
http://lists.boost.org/mailman/listinfo.cgi/boost-build
