This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Newlib usage in eCos (tool-chain question)
- From: Gary Thomas <gary at mlbassoc dot com>
- To: Karel Gardas <kgardas at objectsecurity dot com>
- Cc: eCos Discussion <ecos-discuss at ecos dot sourceware dot org>
- Date: Mon, 02 Jan 2006 06:27:35 -0700
- Subject: Re: [ECOS] Newlib usage in eCos (tool-chain question)
- References: <Pine.LNX.4.63.0601021128230.4555@silence.gardas.net>
On Mon, 2006-01-02 at 11:31 +0100, Karel Gardas wrote:
> Hello,
>
> while I'm playing with eCos last month, I'm just more and more curious
> what's the newlib usage in the tool-chain/eCos pair. Newlib is build as a
> part of GCC, but while linking eCos app it seems of no use which seems to
> be also forced by -nostdlib switch. 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.
--
------------------------------------------------------------
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