On the fine day of Tue, 09 Nov 2004 18:11:19 +0100 Vincent Schut <[EMAIL PROTECTED]> said very eloquently:
> That could well be. I also just installed on a Gentoo machine, and > have the same problem. The files in /usr/local/lib that are created > are libdbmail.0.0.0, libdbmail.0 (link to libdbmail.0.0.0) and > libdbmail (link to libdbmail.0) and the static lib files (.la and .a). > The libs that are created in /usr/local/lib/dbmail suffer from the > same problem: no .so.x.x.x, but just .0.0.0 and .0 as extensions. > However, renaming libdbmail.0.0.0 to libdbmail.so.0.0.0, removing the > other 2 links, and then running ldconfig (which recreates a > libdbmail.0 which links to the .so.0.0.0) seems to be a workaround. I > don't get any errors when starting /etc/init.d/dbmail-lmtpd, and an > ldd on /usr/local/sbin/dbmail-lmtpd finds all libraries. I experienced something vaguely similar while trying out dbmail on Gentoo. I don't think this is the same as what you are talking about, but just in case.... I was getting some linking errors because it was looking for files in /var/tmp/portage. It turned out that the ebuild I was using was mistakenly copying some temporary scripts that shouldn't be installed. I fixed it by doing a make install. Allen
pgp65foMwpuo0.pgp
Description: PGP signature
