This is the mail archive of the
glibc-linux@ricardo.ecn.wfu.edu
mailing list for the glibc project.
Re: strip makes libs unusable
- To: glibc-linux at ricardo dot ecn dot wfu dot edu
- Subject: Re: strip makes libs unusable
- From: Andreas Schwab <schwab at suse dot de>
- Date: 01 Oct 1999 16:04:42 +0200
- References: <40D90446A164D311B0F800508B44E1823CBEF0@exchphx01.microtest.com> <37F3D128.23007CD3@tconl.com>
- Reply-To: glibc-linux at ricardo dot ecn dot wfu dot edu
Joseph Fago <cfago@tconl.com> writes:
|> > "Jones, Clay" wrote:
|> >
|> > I seem to recall that when I rebuilt the latest e2fs utilities, I made them
|> > with the ELF_SHARED option. The resulting shared library and executables were
|> > huge though.
|> >
|> > So I stripped mke2fs, e2fsck, and libext2fs.so.2.
|>
|> Tell me this isn't happening... please folks, don't go stripping your
|> shared libs. You may save a few 'bytes', on large libs maybe a few KB,
|> but it isn't worth it.
|>
|> What do you do when some program needs a function, but you don't know
|> what library to link with? Which one is it in? You could have run 'nm'
|> to find out... but wait, all the symbols are gone.
What are you talking about? The dynamic symbol table is still there.
|> nm shows:
|> nm ./libext2fs.so.2
|> ./libext2fs.so.2: no symbols
RTFM. nm -D lists the dynamic symbols.
--
Andreas Schwab "And now for something
SuSE Labs completely different."
schwab@suse.de
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg