It fails to compiling with the kerberos useflag. It can always be reproduced with the keberos use flag on when compiling. As far as I remember it had something to to with libasn from the kerberos package. Reproducible: Always Steps to Reproduce: 1. USE=kerberos emerge /usr/portage/net-mail/evolution/evolution-1.4.0.ebuild 2. 3. Actual Results: Compile fails with an error about libasn Expected Results: Compiled with kerberos support
can you attach a complete build log and also the output of emerge info? also, which version of kerberos do you have installed? mit-krb5 ?
I probably can try unemerging my now working evolution (without kerberos). I use the mit-krb5 because I thought that this was the one which the new kerberos ebuild would be based of (because it uses the krb4 use flag...I am using both, maybe that is the problem...evolution doesn't know which to use?) I will try to figure out if it is really the krb4 use flag making the problems. Regards Hasse
you don't have to unmerge it as such, could you do something like : USE="kerberos" ebuild /usr/portage/net-mail/evolution/evolution-1.4.0.ebuild clean unpack compile 2>&1 | tee /tmp/evo-1.4.kerberos.log the ebuild is configured to only enable kerberos v5 though.
Created attachment 13210 [details] this is emerge info output Here is the requested emerge info output
Created attachment 13211 [details] this is the build log this is the requested build log
Hi Sorry for my slow feedback. I have now created the requested attachments. Hope it helps you
from the log, it looks like /usr/lib/libasn1.so is trying to include /usr/lib/libcom_err which is conflicting versions. can you find out what package /usr/lib/libasn1.so belongs to? by doing : etcat belongs /usr/lib/libasn1.so
It is heimdal which is making the conflict. I have just unmerged it. I really don't need it, I prefer the mit-krb5, but wouldn't it be a good idea making heimdal and mit-krb5 conflicting packages. They are providing the same function.
i believe someone is working on that issue as we speak. the kerberos stuff is being reorganised in such a manner. could you let me know if the compile succeeds for you now? thanks
Yes it works now without heimdal. Thanks for the help :-)
thanks for the confirmation.