Re: [HACKERS] Problem with dlopen and PostgreSQL - load of file failed - Mailing list pgsql-hackers

From Jaromir Dolecek
Subject Re: [HACKERS] Problem with dlopen and PostgreSQL - load of file failed
Date
Msg-id 199907251902.VAA24848@jdolecek.per4mance.cz
Whole thread Raw
In response to Re: [HACKERS] Problem with dlopen and PostgreSQL - load of file failed  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] Problem with dlopen and PostgreSQL - load of file failed
List pgsql-hackers
Tom Lane wrote:
> "D'Arcy" "J.M." Cain <darcy@druid.net> writes:
> > ERROR:  Load of file /usr/pgsql/modules/glaccount.so failed: dlopen (/usr/pgsql/modules/glaccount.so) failed
> 
> > The error message isn't very informative.
> 
> Dynamic loaders tend to be pretty horrid about that :-(.  My bet is
> a failure to resolve an external reference to another shared library.
> Try using "ldd" (or local equivalent) on the shlib to find out what
> other shlibs it depends on.  Be suspicious if ldd fails to show all the
> dependencies you expect (eg, practically anything will depend on libc);
> that probably means the linker failed to locate the other shlib when
> linking this one.  Next make sure all those other shlibs are in the
> right places, and are known to the system if your system keeps a table
> of shlibs.  Then start checking *their* dependencies...

Further lossage - ELF vs. a.out: when calling() dlsym(3), a.out
needs the symbols prepended with underscore, but ELF doesn't. Got bitten
by this bit when helping garbled with ClanLib ...
You might check the source if a.out systems are handled right ....

-- 
Jaromir Dolecek <dolecek@ics.muni.cz>      http://www.ics.muni.cz/~dolecek/
"The only way how to get rid temptation is to yield to it." -- Oscar Wilde


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Problem with dlopen and PostgreSQL - load of file failed
Next
From: Cd Chen
Date:
Subject: A multi-lang patch for psql 6.5.1