From: Pete Buechler <peterb@suse.com>
To: Ruedi.Hofer@ascom.ch, linuxppc-embedded@lists.linuxppc.org
Cc: distribution@linux01.hasler.ascom.ch
Subject: Re: newlib, uclib
Date: Thu, 6 Jul 2000 07:59:48 -0700 [thread overview]
Message-ID: <00070608033801.21103@CX579290-B> (raw)
In-Reply-To: <0FXA0055X023NC@pmdf-it.hasler.ascom.ch>
On Thu, 06 Jul 2000, Ruedi.Hofer@ascom.ch wrote:
>
> Hi
>
> In order to build a commercially successful product I have to reduce the footprint of the system.
> Having a quick look at the files showed me, that the largest files are the libs (libc.so.6 = 4M) ... as u all know.
> When searching the web for replacements, I came across newlib and uclib.
>
> Is anyone out there who has done some work with this libs?
>
> Are they easy to use, install, build?
>
> Are there other (small) replacements for the libc?
>
> /Ruedi
>
4M sounds like the unstripped size. Make sure you strip the symbols from the
libraries if you are desperate for disk space. Newlib is an implementation of
the C library, but it was intended for use on embedded systems without Linux.
Hence there is no support for the Linux system calls in it.
Another option is to identify the C library functions that you are actually
using and remove the others from the archive. That would be rather tough by
hand. Lineo has a closed source tool called "Lipo" which will do that for you -
there may be a free replacement in the works somewhere.
--
Pete Buechler : SuSE Linux Developer
Work e-mail : peterb@suse.com
Work web page : http://www.suse.com/~peterb
Personal e-mail : peter.buechler@home.com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-07-06 14:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-06 13:29 newlib, uclib Ruedi.Hofer
2000-07-06 14:26 ` Tom Roberts
2000-07-06 16:57 ` Wolfgang Denk
2000-07-06 14:59 ` Pete Buechler [this message]
2000-07-06 15:14 ` Frank Smith
-- strict thread matches above, loose matches on Subject: below --
2000-07-10 17:48 Eric Vaitl
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=00070608033801.21103@CX579290-B \
--to=peterb@suse.com \
--cc=Ruedi.Hofer@ascom.ch \
--cc=distribution@linux01.hasler.ascom.ch \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.