Wednesday, November 03, 2004

Shared Library Woes

Pulled down Sun's J2EE SDK, and ran the installer, which couldn't find Found what I thought was the Gentoo package, but all were masked. Set ~x86 in ACCEPT_KEYWORDS in /etc/make.conf, emerged, and tried the installer again; no luck. Googled, and found that the file is part of the libstdc++2.10-glibc2.2 package; did emerge search, but didn't find it. qpkg -f turned up nothing. Googled again, found libstdc++2.10-glibc2.2 in a .deb file on

Okay, now how do I pry apart a .deb file on a Gentoo system? Wikipedia knew; it's an ar file, that contains .tar.gz files. No sweat, extracted the file, the installer didn't find it; remembered to run ldconfig; didn't find it; looked for the file; didn't find it. what!?

Re-extracted it, looked closer, and saw that it's just a link; extracted the link target, copied that as the link name, ran ldconfig, ran the installer, found it; whew.

I couldn't imagine that Gentoo didn't have this somewhere, so went back and searched the forums. Didn't find it. Googled for it, saying ''. Found it, it's in lib_compat. emerged that, and life's good.


Blogger Rob said...

Sounds like Windows DLLs are less of a pain...

10:30 AM  
Blogger djaquay said...

Perhaps. Providing what you need is certainly less of a pain. Sun didn't. An improvement would be a better way to know where a certain file is, package-wise. I mentioned qpkg, but that only reports on installed files, so it was of no help this time. But I also learned better how to find things, so the length of this affair would be much shorter next time.

10:42 AM  

Post a Comment

<< Home