[NTLUG:Discuss] Re: DBD Driver Installation Issue

[kbrannen@gte.net]

Dennis Daupert wrote:
> D'oh! Will do. This morning I received a diagnosis from the DBD::Ingres
> module maintainer, saying there is a missing library. He directed me to
> "find out which standard library contains 'clock_gettime' and ensure
> that it is loaded."
> 
> I'm not yet up to speed on mysterious things like checking libraries,
> installing
> new libs, etc. I'd be very interested to see a presentation at NTLUG on
> these matters. Meanwhile, I've posted a query on comp.unix.solaris for
> that info. I imagine much of it would be comparable to doing libraries
> on linux, but I've asked the question there in case there are any
> solaris specific items.

It's not that hard.  There's a cool utility called "nm" that can do this for 
you; you need to read the man page for it to help interpret the output though. 
  But you can "cd /lib" (and /usr/lib and whereever else your libs are) and do 
something like:

[166 ~ /lib] nm -pog lib* | grep clock_gettime
librt.so.1:00003fa4 T clock_gettime
[167 ~ /lib]

(I think nm's args will be slightly different on solaris, IIRC.)  Here we find 
that librt.so.1 contains code text labeled clock_gettime, meaning it has that 
function defined because of the name and the "T".  Your solaris system may put 
it in another library, but this sort of command will work on all unix systems 
(including Linux. :-)  Note, I did this on my SuSE-Linux 8.0 system.

Perhaps I'm forgetting what it's like to be newbie in this area because I've 
been doing this for so long, :-) but a presentation on this subject matter 
wouldn't take more than about 10 minutes, there's just not that much there. 
If you understand the /basics/ of rpm (or tar depending on your distro), nm, 
ldd, ldconfig, and ld (the linker which is normally invoked with gcc), then 
you understand about 99% of all there is to know here.  Check out the man 
pages yourself, it fun (for some definition of fun. :-)

HTH,
Kevin