libbind.so unresolved symbols
From: ldg@ulysium.net
Date: 04/24/03
- Previous message: Pshyk, John: "Additional Info: %CPU Shows "??""
- Next in thread: ldg_at_ulysium.net: "summary: Re: libbind.so unresolved symbols"
- Reply: ldg_at_ulysium.net: "summary: Re: libbind.so unresolved symbols"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 24 Apr 2003 14:32:53 -0400 From: ldg@ulysium.net To: Tru64 Unix managers <tru64-unix-managers@ornl.gov>
Hello all,
I compiled the latest sendmail with support for bind, of which I have place
it's includes and libraries in /usr/local/bind/include and
/usr/local/bind/lib
The bind version is 9.2.2 and tru64 is 5.1b
I added a line in the sendmail startup script from /sbin/init.d to specify
LD_LIBRARY_PATH to prevent the loader from not finding the libbind.so file,
and it is found, however there is an unresolved symbol in it that I can't
find.
I added _RLD_ARGS in the sendmail startup script with a few flags to try to
get more detailed info but I'm not getting the info about which symbol is
actually unresolved. I tried this with the -v and -interact flags, the -v
gives me a lot of info but not the one I need, and -interact isn't prompting
for the path needed as I thought it would.
I used nm on libbind.so but it lists the contents without specifying where
those symbols will be expected to come from.
What else should I try to find out which symbol is actually unresolved, and
perhaps which file it's expected to come from?
Is there an other environment variable I can set besides the LD_LIBRARY_PATH
that may help it find its parts?
-- Didier Godefroy mailto:dg@ulysium.net
- Previous message: Pshyk, John: "Additional Info: %CPU Shows "??""
- Next in thread: ldg_at_ulysium.net: "summary: Re: libbind.so unresolved symbols"
- Reply: ldg_at_ulysium.net: "summary: Re: libbind.so unresolved symbols"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]