[PATCH] Static linking binaries with uClibc
Will Newton
will.newton at gmail.com
Thu Feb 4 11:00:46 UTC 2010
On Thu, Feb 4, 2010 at 10:42 AM, Bernhard Reutner-Fischer
<rep.dot.nop at gmail.com> wrote:
> On Thu, Feb 04, 2010 at 10:27:22AM +0000, Will Newton wrote:
>
>>IMO this weak stuff is a holdover from the old days of ELKS etc., I'm
>>not sure if it really is that useful any more.
>
> If i don't need stdio, then i don't want it being pulled in. If you
> don't care, then you can as well live with this difference for
> a simple write();return; program:
> $ size static_stdio{,_glibc}
> text data bss dec hex filename
> 2572 128 36 2736 ab0 static_stdio
> 512074 1928 6988 520990 7f31e static_stdio_glibc
> I, personally, prefer the 3k variant over the 500k one.
500k? I rarely have a uClibc above 200k, not sure how you have managed
to make one so large.
What does the app actually do though? What is the use case for
stdio-less apps in a static linked environment? I argue it is close to
no use, and the fact that it has been broken for years and no-one has
fixed it rather backs me up on that.
More information about the uClibc
mailing list