This is the mail archive of the libc-alpha@sources.redhat.com mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Statically linked binary way way too big


On 16 October 2002 16:22, Geoff Keating wrote:
> Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua> writes:
> > On 16 October 2002 05:13, Momchil Velikov wrote:
> > > >>>>> "Denis" == Denis Vlasenko
> > > >>>>> <vda@port.imtp.ilyichevsk.odessa.ua> writes:
> > >
> > > Denis> Oh, and here is the source code of that program:
> > >
> > > Denis> int main() {
> > > Denis>         return 0;
> > > Denis> }
> > >
> > > So, what's wrong ? This program being 400k does not imply a
> > > 6-lines program would be 800k.
> >
> > I know. Basically we suck in half of C lib into empty program.
> >
> > >  In a real program startup file costs will
> > > quickly disseminate throughout the useful code. (that's not to
> > > imply the startup files are not useful ;)
> >
> > A real program (part of glibc): sln
>
> Most real programs, including sln, have to use stdio anyway to report
> errors, and this drags in all the i18n machinery.

gcc3.2-compiled sln from glibc2.3 takes even less bytes than my "empty"
proggie compiled by gcc 3.0.3 against glibc 2.2.5 (good, at least here
we have negative trend on size ;-)

So it cannot be i18n - my program obviously does not need it.
Is it get linked in anyway? 8-(
--
vda


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]