On Monday, October 28, 2002, at 10:21 AM, Gerald Waugh wrote:
On Mon, 28 Oct 2002, Parker Morse wrote:But the rpm still fails that dependency. How can I find out where it's looking for libJudy.so, so I can put a link there?try putting it in /lib/
OK, I've tried that. No luck.
[root morse]# rpm -i --test db3-3.3.11-6.i386.rpm error: failed dependencies: libc.so.6(GLIBC_2.2) is needed by db3-3.3.11-6
[snip]
meet this dependency, or should I try to find another way to get libdb-3. 3. so? (Any suggestions?)Not sure about this one! It might screw up future blue-link updates and packages(3) Am I doing this the hard way? Should I be working from the source tarball instead of the RPM?It probably doesn't make much difference, a dependency is a dependency
Yes, I suppose if it's using Berkeley DB, it's going to need it whether I install from source or from RPM.
Interestingly, Berkeley DB is apparently now around 4.1, so I'm dubious about that working if I installed it from source - assuming I could.
Still, perhaps I could find an older RPM that installs libdb-3.3.so which doesn't require the newer glibc? Every likely-looking rpm on rpmfind.com is asking for that newer glibc, if that is indeed what it's asking after.
pjm