Fernando de Oliveira wrote:
> I understand that. But for packages which have "big" sizes and/or
> build times, I believe it would be good to include optional stripping
> instructions, again, not only for practical, but also for educational
> purpose.
I agree with that.
> Some criteria could be used to define what "big" means in terms of
> sizes and build times (of course, this in SBU). Or instead of
> describing it in some packages, a small paragraph could be added to
> "Notes on Building Software" (have just looked at it a moment ago and
> again think how good instructions there are there).
>
> As I wrote before, I have many doubts about this strip thing. For
> example, how to avoid this kind of warnings:
>
> "strip:OpenJDK-1.7.0.9-2.3.4/jre/lib/rhino.jar: File format not
> recognized"
Try something like:
find /lib /usr/lib /opt/kde/lib -name \*.so.* -type f -exec strip -d {} \;
From executables, you can do the same but use --strip-unneeded or
perhaps --strip-all. I'd need to experiment.
> or is it possible that after stripping, a package will stop running for
> some reason and I will have to build it again? This question made me do
> the opposite of striping: increase the space occupied by a package.
> How? Keeping the original not-stripped, just in case. I am not doing it
> anymore.
If you do -s (--strip-all) on a library, I think it can make it unusable.
> Other question: should I always use "--strip-unneeded", I am not doing
> it in OpenJDK, only with LibreOffice.
>
> If BLFS is not including these explanations, is there a good page to
> learn about these matters?
It's mentioned in LFS, both in Chapter 5 and Chapter 6.
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
