On Fri, Mar 18, 2011 at 10:39 AM, David Paterson <dnpaterson@xxxxxxxxx> wrote:
>
> It is, I agree, quite hard to understand. My attempts so far at
> putting Newlib into the GCC directory haven't had much success :{
>
> I'll keep trying...
I'm not having much success at all.
I've put the added the Newlib sources to the GCC source directory - an
additional directory at the top level. I've created
$PREFIX/$TARGET/sys-include and copied the Newlib/newlib/libc/include
files, and the $PREFIX/include files into it (it wouldn't build
without the latter for some reason - I tihnk if sys-include is there
the other include directories are ignored).
I can get GCC to build OK, but Newlib is just ignored. I thought the
configure and make commands were set up to go recursively down the
tree, processing any "configure" and "Makefile" entries they found,
but that doesn't seem to happen. I've tried to figure out what I need
to do to build Newlib, but have to admit I'm more than a little
baffled by the intricacies of the configure and make systems.
I may have to leave this for now, since I do have a method that works
(if a little less than ideally efficient) and concentrate on
completing the board support package before my team mate arrives with
the hardware :-)
It seems there's quite a long (and steep) learning curve to
understanding the mysteries of GCC...
David
