The configure script won't find sasl2 with gcc3.x, because /usr/include is given as include-path in the configure-test for sasl2, so that the compiler prints out a warning. The configure-script interpets this as missing sasl2, so the emerge fails: --- snip --- checking for sasl/sasl.h... no configure: error: Cannot continue without libsasl2. Get it from ftp://ftp.andrew.cmu.edu/pub/cyrus-mail/. !!! ERROR: The ebuild did not complete successfully. !!! Function src_compile, Line 28, Exitcode 1 !!! bad ./configure !!! emerge aborting on /usr/portage/net-mail/cyrus-imapd/cyrus-imapd-2.1.5-r1.ebuild . --- snip --- This may happen with other packages containing configure scripts not ready for gcc3, too... Jojo
It's not gcc3 related. Is you unset ssl in your USE, it detects sasl/sasl.h correctly, and the package compiles and installs...
cyrus-imapd-2.1.9 has been released into portage which fixes this compile problem. Please test and report back on this bug with your experience.
Yes, sasl stuff is fixed, thanks :) One problem I see with this ebuild (and previous), is that it overwrites /var/log/auth.log and /var/log/imapd.log when it's merged... Those files are writen by the syslog daemon, so they need not be created when installing the package, do they?
strange. There is nothing in the ebuild that creates those directories... only a comment saying how to log to those files properly. do you find /var/log/auth.log and /var/log/imapd.log in /var/db/pkg/net- mail/cyrus-imapd-2.1.9/CONTENTS? If not then those files shouldn't be squashed during updates/upgrades... Please let me know.
Hi, here are the first few lines of the CONTENTS file you told me to look: dir /etc dir /etc/pam.d obj /etc/imapd.conf 94c2f71f7ca80b710fb4854e908d712b 1031732901 dir /etc/init.d dir /var dir /var/log obj /var/log/auth.log d41d8cd98f00b204e9800998ecf8427e 1031732901 obj /var/log/imapd.log d41d8cd98f00b204e9800998ecf8427e 1031732901 dir /var/imap dir /var/imap/db [....]
The cyrus-imapd-2.1.9.ebuild has been updated so that the empty log files are not installed on software upgrades. Thanks for noticing the bug!
