On Fri, Oct 28, 2011 at 10:42 PM, Bruce Dubbs <bruce.du...@gmail.com> wrote: > > Well, --strip-unneeded doesn't, but --strip-all on libraries does > because I think using that would basically destroy static libraries. The > chance of a user using a wildcard with that is reasonably high. > > Do we have a specific amount of space saved by that procedure? Is it > significant? >
--strip-all on all libraries is definitely the wrong thing to do, as it breaks the static libraries. According to the article Dan linked, --strip-unneeded is identical to --strip-all, except that for static libraries it keeps the global tables which the linker uses during compilation. This makes me wonder... in chapter 5's stripping, this statement implies that --strip-unneeded actually breaks static libraries: "Take care not to use --strip-unneeded on the libraries. The static ones would be destroyed and the toolchain packages would need to be built all over again." Perhaps with an older version of strip, --strip-unneeded didn't behave as this discussion is implying. Jonathan -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
