From: Mark Hatle <fray@mvista.com>
To: Erik Christiansen <erik@dd.nec.com.au>
Cc: Darin.Johnson@nokia.com, linuxppc-embedded@lists.linuxppc.org
Subject: Re: glibc vs. newlib
Date: Mon, 07 Apr 2003 01:05:23 -0500 [thread overview]
Message-ID: <3E911523.5050607@mvista.com> (raw)
In-Reply-To: <20030407014717.GA742@dd.nec.com.au>
Erik Christiansen wrote:
> On Fri, Apr 04, 2003 at 07:30:21PM -0600, Mark Hatle wrote:
>
>>I strongly recommend you stay away from newlib.
>
>
> Mark,
>
> Is it something related to linux that has given you a bad experience
> with newlib? (There is no related information in your post, so I'm
> curious.)
>
In my experience, the only thing newlib is useful for is bootstrapping a system.
If you have a working system with newlib, more power to you. I have never had
any success or desire to get that to work. For a small system libc, uclibc
looks promising. For a more traditional linux system, glibc is truely the only
way to do it. (With special tools you can dramatically reduce the size of
glibc, but not as far as most people would like.)
--Mark
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-04-07 6:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-04 23:08 glibc vs. newlib Darin.Johnson
2003-04-04 23:19 ` Gary D. Thomas
2003-04-04 23:38 ` Wolfgang Denk
2003-04-05 1:30 ` Mark Hatle
2003-04-07 1:47 ` Erik Christiansen
2003-04-07 6:05 ` Mark Hatle [this message]
2003-04-08 16:36 ` Marius Groeger
2003-04-08 16:27 ` Mark Hatle
[not found] ` <3E92FABD.8050307@imc-berlin.de>
2003-04-08 17:03 ` Mark Hatle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3E911523.5050607@mvista.com \
--to=fray@mvista.com \
--cc=Darin.Johnson@nokia.com \
--cc=erik@dd.nec.com.au \
--cc=linuxppc-embedded@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).