--- Em sex, 25/1/13, Armin K. escreveu:
> De: Armin K.
> Assunto: Re: [blfs-book] r10979 - in trunk/BOOK
> Para: "BLFS Book Maintenance List"
> Data: Sexta-feira, 25 de Janeiro de 2013, 22:06
> On 01/26/2013 01:56 AM, Randy
> McMurchy wrote:
> >
> wrote these words on 01/25/13 18:40 CST:
> >> Author: krejzi
> >> Date: Fri Jan 25 16:40:55 2013
> >> New Revision: 10979
> >>
> >> Log:
> >> Package updates, see changelog for details.
> >> <screen><userinput>autoreconf
> -fi &&
> >> -./configure --prefix=/usr
> \
> >> +./configure CFLAGS="-O2" CXXFLAGS="-O2"
> \
> >> +
> --prefix=/usr
> \
> >>
> --sysconfdir=/etc
> \
> >>
> --enable-texture-float
> \
> >>
> --enable-gles1
> \
> >> @@ -220,16 +221,6 @@
> >>
> >> + <parameter>CFLAGS="-O2"
> CXXFLAGS="-O2"</parameter>: By default,
> >> +
> <application>Autoconf</application> sets CFLAGS
> and CXXFLAGS to
> >> + "-g -O2". That results in
> binaries and libraries being built with
> >> + debugging symbols which make
> them bigger. We override default
> >> + flags to ommit -g switch so
> the final libraries are smaller.
> >> + </para>
> >
> > I do not see why we just cannot give instructions to
> strip the binaries instead
> > of passing flags to configure. That makes no sense. For
> instance, the Gimp
> > creates a 35MB binary executable that can be stripped
> down to less than 6MB but
> > we do not mention that. I'd bet most experienced
> BLFSers strip libs and binaries
> > as a matter of course after building. Passing flags to
> configure is just extra
> > confusion, for no reason.
...
> -g flag was always ommited from MesaLib before it started to
> migrate to
> Autotools (pre 9.0).
>
> After that I didn't know a proper way to remove it, so I
> added the
> instructions to strip the libraries. While updating to 9.0.2
> I consulted
> with people on #dri-devel channel on Freenode and they
> pointed me to that.
>
> When you override CFLAGS and CXXFLAGS, build directory is
> 1GB smaller
> than with default ones. And installed files are at least 50%
> smaller than.
...
> I'll see what I can do, but I still like the idea about
> CFLAGS and
> CXXFLAGS and yes - I am aware that disk space is cheap
> nowadays, but
> that doesn't affect disk space only, but runtime, too ...
> Loading 5MB
> library is always faster than loading 50MB one ...
OpenJDK is a package which would be better stripped. Recently
they have included debugging symbols, resulting in much bigger
binaries. I have been helped by DJ (if recall correctly) to do it, so,
now, I have a reduction in size from about 454M to 132M. It would be
good to include some explicit form of stripping it in the book. At the
moment, I use
find OpenJDK-${VERSION} -type f -exec strip --strip-debug '{}' ';'
Another package where strip instructions could be included is
LibreOffice, although gain is relatively much smaller. At the moment, I
am using:
find libreoffice-${VERSION} -type f \
-exec strip --strip-debug '{}' ';' 2>/dev/null &&
find libreoffice-${VERSION} -type f \
-exec strip --strip-unneeded '{}' ';' 2>/dev/null &&
after a suggestion from Tobias Gasser in (unfortunately, archives are
still down)
<quote>
Re: [lfs-support] A startup quesion
Wednesday, 21 Nov 2012
De:
"Tobias Gasser" ...
Para:
"LFS Support List"
</quote>
The instructions for OJDK should be OK, as they have been given
explicitly. However, the ones for LO, I inferred from a "snippet" from
Thomas, so I am not sure how correctly I have understood them. IMHO, one
more point to explicitly include instructions in the packages pages.
It would be educational, as many, like me, might have doubts about
stripping and would have more examples to learn from.
[]s,
Fernando
--
http://linuxfromscratch.org/mailman/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
