From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] RTLD_DEEPBIND and uClibc
Date: Thu, 17 Jan 2013 22:51:42 +0200 [thread overview]
Message-ID: <50F8645E.2090600@petroprogram.com> (raw)
In-Reply-To: <201301172138.34789.yann.morin.1998@free.fr>
17.1.2013 22:38, Yann E. MORIN kirjoitti:
> Stefan, All,
>
> On Thursday 17 January 2013 Stefan Fr?berg wrote:
>> 17.1.2013 19:44, Yann E. MORIN kirjoitti:
>>> The full set of libraries from a full-blown eglibc, for an ARM gnueabihf
>>> target, is:
>>> Unstripped Stripped
>>> Only eglibc libs 3.6MiB 2.3MiB
>>> With gcc's libs 8.8MiB 3.0MiB
>>>
>>> And for a relatively complete uClibc for x86_64 target:
>>> Unstripped Stripped
>>> Only eglibc libs 2.0MiB 1.0MiB
>>> With gcc's libs 6.9MiB 1.9MiB
>>>
>>> (gcc libs: libstdc++ and libgcc_s)
>>> (These are not the same architecture, but I went for the toolchains I have
>>> locally)
>>>
>>> So, typically, speaking only about the C library libs, the gain would be
>>> around ~1.5MiB.
>> Here's the contents of my target /lib
> [--SNIP--]
>> As you can see from the top of the line the total sum of uClibc + *all
>> the other stuff (pam etc..)* is just
>> 1.4 MB (the size of libuClibc-0.9.33.2.so itself is just 690 KB)
> uClibc == libuClibc.so + libutil.so + ld-uClibc.so + librt.so + libnsl.so
> + libm.so + libdl.so + libcrypt.so
>
> Which totals around 905KiB in your case. Just about the number I gave
> you in my previous mail (mine was exactly 1004KiB). And the eglibc numbers
> are for the same set of libraries (plus all the libnss libs uClibc does
> not have).
>
>> So uClibc wins this round :-)
> Yes, in absolute numbers, uClibc *is* smaller than (e)glibc.
> We *never* said it was bigger.
>
> What Thomas and I are saying, is that you gained about 1.5MiB on your
> 520MiB filesystem. That's about a 0.29% gain. Was that worth the hassle?
> (Beside learning, of course.)
My gentoo box with similar configuration is 1500 MB. So yeah I think it
was worth the hassle :-)
Regards
Stefan
next prev parent reply other threads:[~2013-01-17 20:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 12:51 [Buildroot] RTLD_DEEPBIND and uClibc Stefan Fröberg
2013-01-16 23:00 ` Thomas Petazzoni
2013-01-17 0:36 ` Stefan Fröberg
2013-01-17 8:31 ` Thomas Petazzoni
2013-01-17 13:50 ` Stefan Fröberg
2013-01-17 16:18 ` Alex Bradbury
2013-01-17 16:51 ` Stefan Fröberg
2013-01-17 17:09 ` Alex Bradbury
2013-01-17 18:48 ` Stefan Fröberg
2013-01-17 22:03 ` Peter Korsgaard
2013-01-17 17:44 ` Yann E. MORIN
2013-01-17 18:47 ` Stefan Fröberg
2013-01-17 20:38 ` Yann E. MORIN
2013-01-17 20:41 ` Yann E. MORIN
2013-01-17 20:51 ` Stefan Fröberg [this message]
2013-01-17 21:17 ` Yann E. MORIN
2013-01-17 21:23 ` Stefan Fröberg
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=50F8645E.2090600@petroprogram.com \
--to=stefan.froberg@petroprogram.com \
--cc=buildroot@busybox.net \
/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