[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Nano-devel] the compiled size of nano

From: Mike Frysinger
Subject: Re: [Nano-devel] the compiled size of nano
Date: Sun, 7 Feb 2016 22:39:40 -0500

On 07 Feb 2016 19:51, Benno Schulenberg wrote:
> On Sun, Feb 7, 2016, at 01:11, Mike Frysinger wrote:
> > On 06 Feb 2016 19:03, Mike Frysinger wrote:
> > > On a current Linux system, the size of nano is unchanged.
> > 
> > i verified this statement after each patch in this series.
> For me, before the patches, nano was 145480 bytes,
> after applying all 8 patches, it was 149588 bytes.
> (Stripped.)
> Not a big difference, but still... some three percent.
> But what I noted most: 'configure' takes at least twice
> as long, :(, and 'make' creates a freaking lot of output.
> Could the latter be silenced?
> > my system:
> >   linux-4.4.0
> >   glibc-2.22
> >   gcc-5.3.0
> Mine:
>     linux-2.6.32
>     glibc-2.14
>     gcc-4.4.3

well, those versions are old and have known bugs.  you'd have to look
at the configure output to see what's being detected as broken.  you
can start with the objects actually created under lib/ and the symbols
each contain.

all in all, i'd say it's WAI.

the configure output/time does increase quite a bit because gnulib is
testing a lot of C library functionality to see if it's correct.  i
don't have a good answer there.

what i normally do (as a general rule) is use the -C flag w/configure.
then repeat runs are pretty fast.

Attachment: signature.asc
Description: Digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]