I hate being behind the times. Are there any tools for determining what
libraries (or resources) such executables could make use of?
( than running the executeable with a debugger and watching what it
attempts to open.)
George Wyche

>Date: Mon, 8 May 2006 11:17:16 -0400
>From: Charles Shannon Hendrix <shannon (AT) widomaker (DOT) com>
>To: The Rescue List <rescue (AT) sunhelp (DOT) org>
>Subject: Re: [rescue] Sun Kit Needed for EE Student Here
>
>[SNIP]
>You do not have to load shared libraries at exec time, so it has become
>popular to have the program decide, AFTER it loads, which libraries to load
>and use.
>
>See the PSIX dlopen, dlclose, dlerror, dlsym functions for more information.
>
>[SNIP]
Please see the dynamic loading functions for more information. Not
>all shared libraries have compile-time bindings.
>[SNIP]
>I've dealt with this a lot when building packages for distribution,
>because you can no longer just check what a binary links against
>to determine what its dependencies are.
>
>Fortunately, most applications that do this are graceful about it,
>telling you at runtime what is missing, or just silently doing without
>the features provided by the missing libraries.
>
>For example, if you load Amarok (music player) and it cannot find the
>gstreamer libraries, it will automatically switch to another sound engine, and
>will disable features dependent on gstreamer.
>

>shannon "AT" widomaker.com [SNIP]
rescue list -