From: Mark Hatle <fray@mvista•com>
To: James Don <JDon@spacebridge•com>
Cc: "'linuxppc-embedded@lists•linuxppc.org'"
<linuxppc-embedded@lists•linuxppc.org>
Subject: Re: Whats the "standard" embedded C lib?
Date: Tue, 07 Jan 2003 15:28:24 -0600 [thread overview]
Message-ID: <3E1B4678.5050004@mvista.com> (raw)
In-Reply-To: DB0585C9F6F9D411BE8F00D0B7896A4CC05FC8@SNCMAIL
James Don wrote:
> Hi there,
>
> I am just looking at compiling "busybox". And am now at a point where I need
> to consider more than just the kernel and my bootloader.
>
> I have build my gcc 2.95.3 using newlib (from redhat I believe) ...
newlib is only used as a bootstrap mechanism before you build a "real" C library.
> I am having some troubles building busy box ... as I need to sort our which
> 'headers' to include etc ...
>
> I think I am on the right track to completing this but I read something in
> the busy box makefile that kind of stirred my confidence ... it said uClib
> is best with busy box ... is this the same as newlib?
busybox will work with uclibc or glibc. I recommend glibc, but due to size
limitations you may want to use uclibc. (Be aware that uclib isn't as well
supported on PPC. At least wasn't last time I looked..)
> What embedded C lib do you folks recommend? (for PPC 860 if that matters)
glibc is much larger then uclibc, but is a "full featured" c library (w/ shared
library support). There many ways to shrink down the size of glibc to something
more manageable for an embedded project, but it will probably still not be as
small as uclibc.
--Mark
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-01-07 21:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-07 21:12 Whats the "standard" embedded C lib? James Don
2003-01-07 21:28 ` Mark Hatle [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-07 21:38 James Don
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=3E1B4678.5050004@mvista.com \
--to=fray@mvista$(echo .)com \
--cc=JDon@spacebridge$(echo .)com \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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