It seems like dovecot's configure script doesn't detect the MySQL libraries when they're in /usr/lib64, so the current (0.99.11-2.EL4.1) RHEL4 dovecot package has MySQL support properly built-in on i386, but missing on x86_64. A quick workaround would be adding this before %configure : export CFLAGS="%{optflags} `mysql_config --libs` -fPIC" Please note I've just checked, and this is also true in FC development (1.0-0.beta2.4.1).
Following my attempts to get dovecot with MySQL running, I also noticed that the example LDAP and SQL configurations referenced in the docs are missing from the package. This should be added to %files : %doc doc/*.conf The files are : doc/dovecot-ldap.conf doc/dovecot-sql.conf
Fixed both issues in rawhide.
Looking at the patch that fixes this, I noticed in the sqlite library detection part of configure (which says it's stolen from the mysql code above), the sqlite headers and libraries are found but then the variables that are set are MYSQL_INCLUDE and MYSQL_LIBDIR rather than SQLITE_INCLUDE and SQLITE_LIBDIR. Looks wrong to me! This is also now the only patch that affects autotools input files. Why not edit configure directly and skip running the autotools altogether?
> This is also now the only patch that affects autotools input files. > Why not edit configure directly and skip running the autotools > altogether? Why yes? For the other issue, it indeed looks wrong, i'll check it.
Indeed, the MYSQL_LIBDIR setting for sqlite seems wrong, but that's an upstream mistake apparently. Thanks for the fix that will go in FC5. But now, would it be possible to also add a similar patch to the RHEL4 package? This is really a nasty bug, since the i386 and x86_64 packages end up having different functionnalities.
Fixed also the sqlite detection, will go into next release. When some more issues collect for fc5, will release an update.
Adding devel ACK, see comment #8.
This has been fixed upstream in 1.0beta6.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2006-0439.html