Hello, I read the same page several months ago.
So I checked on a testing system : I stripped existing binaries and shared libraries with "--strip-all", and static libraries with "--strip-unneeded". The system remained fully functional, and subsequent linking operations were all successful. So, the information in this page seems to be correct. However, this should be confirmed by testing during a LFS build, which I have not done so far. "--strip-all" and "--strip-unneeded" give exactly the same result on binaries and shared libraries. Indeed, the most simple could be to use "--strip-unneeded" indifferently on all objects. However, this is only useful for people that wish to have the most minimalist system. Regards, Mickaël Blanchard 2012/8/31 Ragnar Thomsen <rthoms...@gmail.com> > It is stated in LFS that --strip-unneeded should not be used on > libraries, as the static ones will be destroyed. > > I found this page: > http://www.technovelty.org/linux/ > > Which states that --strip-unneeded is safe to use on both shared and > static libraries, while --strip-all is only safe for shared ones. > > Being a minimalist, I am tempted to use --strip-unneeded on all > libraries. Has anyone tried to see if this breaks a LFS system? > > -Ragnar- > -- > http://linuxfromscratch.org/mailman/listinfo/lfs-dev > FAQ: http://www.linuxfromscratch.org/faq/ > Unsubscribe: See the above information page >
-- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
