Summary: | OpenOffice 1.1 fails to link with db-3.2 , links with db-4 instead. (via libnss_ldap) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Zhen Lin <lowzl> |
Component: | Current packages | Assignee: | Paul de Vrieze (RETIRED) <pauldv> |
Status: | RESOLVED INVALID | ||
Severity: | major | CC: | grandmasterlinux, liquidx, mholzer, robbat2 |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Zhen Lin
2003-10-18 20:27:57 UTC
I guess that your nss_ldap is broken and that openoffice just accidentilly stumbled on it. Please try to remerge nss_ldap. I remerged nss_ldap first thing, it only made things worse. (Broke bash, probably via pam) So, I changed the Makefile so that it links with db-3.2 and install that, try [openoffice] again, and same error. This is totally openoffice unrelated. Please do the following: make sure that db-4 is installed. Then remerge openldap, then remerge pam_ldap and nss_ldap. The problem is that you have db library mismatches between openldap and the dependent libraries pam_ldap and nss_ldap. Damn... it didn't work - nss_ldap broke again, I wonder whether pam_ldap did as well. ldd /usr/lib/libldap.so.2 /lib/libnss_ldap.so.2 /lib/security/pam_ldap.so /usr/lib/libldap.so.2: /usr/lib/libdb-3.2.so => /usr/lib/libdb-3.2.so (0x40028000) liblber.so.2 => /usr/lib/liblber.so.2 (0x400c7000) libnsl.so.1 => /lib/libnsl.so.1 (0x400d2000) libresolv.so.2 => /lib/libresolv.so.2 (0x400e6000) libdl.so.2 => /lib/libdl.so.2 (0x400f7000) libkrb4.so.2 => /usr/lib/libkrb4.so.2 (0x400fa000) libdes425.so.3 => /usr/lib/libdes425.so.3 (0x4010f000) libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x40113000) libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x40173000) libcom_err.so.3 => /usr/lib/libcom_err.so.3 (0x40183000) libssl.so.0.9.6 => /usr/lib/libssl.so.0.9.6 (0x40185000) libcrypto.so.0.9.6 => /usr/lib/libcrypto.so.0.9.6 (0x401b3000) libc.so.6 => /lib/libc.so.6 (0x40273000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000) /lib/libnss_ldap.so.2: /usr/lib/libdb-3.2.so => /usr/lib/libdb-3.2.so (0x40018000) libldap.so.2 => /usr/lib/libldap.so.2 (0x400b7000) liblber.so.2 => /usr/lib/liblber.so.2 (0x400de000) libdl.so.2 => /lib/libdl.so.2 (0x400e9000) libnsl.so.1 => /lib/libnsl.so.1 (0x400ec000) libresolv.so.2 => /lib/libresolv.so.2 (0x40100000) libc.so.6 => /lib/libc.so.6 (0x40112000) libkrb4.so.2 => /usr/lib/libkrb4.so.2 (0x40239000) libdes425.so.3 => /usr/lib/libdes425.so.3 (0x4024d000) libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x40251000) libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x402b1000) libcom_err.so.3 => /usr/lib/libcom_err.so.3 (0x402c1000) libssl.so.0.9.6 => /usr/lib/libssl.so.0.9.6 (0x402c4000) libcrypto.so.0.9.6 => /usr/lib/libcrypto.so.0.9.6 (0x402f2000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000) /lib/security/pam_ldap.so: /usr/lib/libdb-3.2.so => /usr/lib/libdb-3.2.so (0x4000a000) libldap.so.2 => /usr/lib/libldap.so.2 (0x400a9000) liblber.so.2 => /usr/lib/liblber.so.2 (0x400d0000) libcrypt.so.1 => /lib/libcrypt.so.1 (0x400db000) libresolv.so.2 => /lib/libresolv.so.2 (0x40108000) libpam.so.0 => /lib/libpam.so.0 (0x40119000) libdl.so.2 => /lib/libdl.so.2 (0x40122000) libc.so.6 => /lib/libc.so.6 (0x40125000) libnsl.so.1 => /lib/libnsl.so.1 (0x4024c000) libkrb4.so.2 => /usr/lib/libkrb4.so.2 (0x40260000) libdes425.so.3 => /usr/lib/libdes425.so.3 (0x40274000) libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x40278000) libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x402d9000) libcom_err.so.3 => /usr/lib/libcom_err.so.3 (0x402e9000) libssl.so.0.9.6 => /usr/lib/libssl.so.0.9.6 (0x402eb000) libcrypto.so.0.9.6 => /usr/lib/libcrypto.so.0.9.6 (0x40319000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000) Hmm, it would seem that openldap links to db-3.2 by default and nss_ldap links to the latest version. But, couple this with the fact that db-4's db185 compatibility isn't causes breakage: nm /usr/lib/libdb-4.0.so | fgrep __db185_open 0000e160 T __db185_open_4000 And how this eventually leads to openoffice compile failure, I have no idea... ls is mentioned, but ls is linked to the correct library... Maybe a failure resolving dependencies during dlopen? As you can see libldap is still linked against libldap is still linked against db-3.2. I think that indeed the ldap people need to look at nss_ldap and pam_ldap and make it link against the same version that openldap is linked against try # revdep-rebuild is this still an issue? Well, I don't get link problems anymore, merely that I can't run the OO.o setup program. (There was some mention of GTK problems...) So I gave up and I use openoffice-bin Closing this |