Summary: | postfix cannot start after emerge (libmysqlclient problem) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | oktay altunergil <oktay> |
Component: | Current packages | Assignee: | Nick Hadaway <grandmasterlinux> |
Status: | RESOLVED FIXED | ||
Severity: | minor | CC: | h3y, woodchip |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
oktay altunergil
2003-03-06 10:04:48 UTC
Same problem here, same cause. Have just emerged the new postfix-2.0.6 and all is well. However, it does mean that the mysql upgrade managed to break postfix; suspect this isn't going to be a big problem since most people will also get the postfix upgrade... Phil if you re-emerge postfix after mysql does the problem of the bad linking go away? Not MySQL, but emerging the latest postfix (postfix-2.0.6) fixes the problem since it's linked against the correct mysql library. (see below) bash-2.05b# ldd /usr/sbin/postfix libssl.so.0.9.6 => /usr/lib/libssl.so.0.9.6 (0x4002d000) libcrypto.so.0.9.6 => /usr/lib/libcrypto.so.0.9.6 (0x4005c000) libmysqlclient.so.12 => /usr/lib/libmysqlclient.so.12 (0x40121000) libm.so.6 => /lib/libm.so.6 (0x40161000) libz.so.1 => /usr/lib/libz.so.1 (0x40183000) libpam.so.0 => /lib/libpam.so.0 (0x40191000) libpcre.so.0 => /usr/lib/libpcre.so.0 (0x4019a000) libdl.so.2 => /lib/libdl.so.2 (0x401a4000) libcrypt.so.1 => /lib/libcrypt.so.1 (0x401a7000) libdb-3.2.so => /usr/lib/libdb-3.2.so (0x401d4000) libnsl.so.1 => /lib/libnsl.so.1 (0x40272000) libresolv.so.2 => /lib/libresolv.so.2 (0x40287000) libc.so.6 => /lib/libc.so.6 (0x4029a000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) Thank you for your help. As far as I am concerned this is not an issue anymore. 2.0.9 will be unmasked soon, thus addressing this bug. closing. |