| |||||||||||||
SELF: Anatomy of an (alleged) failureSELF: Anatomy of an (alleged) failurePosted Jul 10, 2010 12:31 UTC (Sat) by makomk (guest, #51493)In reply to: SELF: Anatomy of an (alleged) failure by nix Parent article: SELF: Anatomy of an (alleged) failure
Yeah, dlopen() problems with not finding libraries in /lib32 don't tend to happen, mostly because it's just easier to do it the right way from the start and let dlopen() search the appropriate directories. (Even on pure 32-bit systems, some libraries are in /lib on some systems, /usr/lib on others, and perhaps even in /usr/local/lib or $HOME/lib if they've been manually installed.)
(Log in to post comments)
SELF: Anatomy of an (alleged) failure Posted Jul 10, 2010 20:24 UTC (Sat) by nix (subscriber, #2304) [Link]
dlopen() doesn't search directories for you, does it? Programs generally want to look in a subdirectory of the libdir, anyway. Nonetheless they almost all look in the right place.
|
|||||||||||||