[buildroot] $(STRIP) --strip-unneeded on a SHARED library...WHY?
John Z. Bohach
jzb at aexorsyst.com
Tue Dec 6 19:12:19 UTC 2005
On Tuesday 06 December 2005 11:08, Rob Landley wrote:
> On Tuesday 06 December 2005 11:20, John Z. Bohach wrote:
> > > we use --strip-unneeded too, and it's fine. but it's fine for
> > > runtime. is it perhaps the case that libraries stripped like
> > > that can no longer be used in development?
> >
> > BINGO. Executables that have been linked have addresses hardwired where
> > the symbols were. The library code didn't change, but '$(LD) ...
> > -l{somelib} ...etc' won't find the symbols, and you'll get undefined
> > symbol errors.
>
> How can there be enough information to resolve the symbol at runtime, but
> not enough information to resolve the symbol at compile time? Runtime
> dynamic linking is still doing a lookup by name on the symbol, last I
> checked.
>
> Rob
Haven't gotten to runtime for those specific packages involved in the
'undefined symbol' errors. Can't get past linking...
More information about the busybox
mailing list