This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Re: Newlib usage in eCos (tool-chain question)
On Mon, 2006-01-02 at 09:34 -0600, Grant Edwards wrote:
> In gmane.os.ecos.general, you wrote:
>
> >> [...] So my conclusion so far is that newlib is in fact not
> >> used while linking any eCos app, since eCos itself provides
> >> all the needed libc/m code.
> >>
> >> Am I right?
> >
> > Yes, 'newlib' is *not* used by eCos. It's required simply as part
> > of the toolchain build process.
>
> I've always wondered why newlib is required as part of the
> toolchain build process, but never found an explanation. Why
> is it not possible to build gcc w/o a library?
I asked the same questions nearly a decade ago and got no good
response :-( I'm sure that part of it was to be able to run some
remote [regression] tests and make sure that all of the pieces were
working, even for crosstool setups. I guess it's just something that
we have to live with.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss