[kwlug-disc] how to identify superfluous shared library references?
L.D. Paniak
ldpaniak at fourpisolutions.com
Tue Mar 10 17:20:15 EDT 2009
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Why don't you start pruning your list of libs, compile, run and see if
anything breaks/complains? No break -> not needed
Too naive? Hope your list of libraries isn't too long...
Robert P. J. Day wrote:
> i'm looking at an executable that was built with a couple dozen "-l"
> references to refer to shared libs to be linked at run time. but only
> a few of those libs are actually used -- the list of libs was copied
> and pasted and is *way* overkill, but if you list them at compile
> time, they're going to show up via "ldd" in the final executable.
>
> is there a way to identify which shared libs are actually being
> *used* by an executable, and which are superfluous and can be dropped
> from the list of libs during the compile step?
>
> they don't hurt, of course, except for taking up a small amount of
> space in the executable, but if they're not necessary, i'd rather they
> not be there. thanks.
>
> rday
> --
>
> ========================================================================
> Robert P. J. Day
> Linux Consulting, Training and Annoying Kernel Pedantry:
> Have classroom, will lecture.
>
> http://crashcourse.ca Waterloo, Ontario, CANADA
> ========================================================================
>
> _______________________________________________
> kwlug-disc_kwlug.org mailing list
> kwlug-disc_kwlug.org at kwlug.org
> http://astoria.ccjclearline.com/mailman/listinfo/kwlug-disc_kwlug.org
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFJttmO8h2PnOHbiQcRAiaxAJ9jE9vkALRXbIRdX1FvPTS55R+cWwCfe9U0
CM0N3uWRh0dR3ABb5g0ytMU=
=4ohd
-----END PGP SIGNATURE-----
More information about the kwlug-disc
mailing list