This is the mail archive of the ecos-discuss@sourceware.org mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Re: What is the current status of the iPaq application? (target)


> This has probably been answered before, but what's broken about
> the gcc ARM target such it that requires newlib?  Or is this an
> eCos requirement?
> 
> I've built GCC cross compilers for embedded use on a half-dozen
> architectures, and none of the others required newlib.

It's not really "broken" and isn't really related to eCos.  You can build a C
only GCC without newlib.  If you want C++ support etc. though, you need a C
library underneath of it.  Newlib is just a solution to that problem.  These
versions of GCC don't make any assumptions the target code running on any OS
(eg. you can build bare on the metal code with them), so they don't make any
assumptions about a C library either.

The typical bootstrap process goes like:

Build binutils
Build bootstrap GCC (C only)
Build newlib
Build full GCC (C/C++)

--Chris

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]