Bugzilla Bug 220571

evolution-2.22.1.1 fails the configure stage when it checks whether pilot-link
can do unicode conversions (I have the latest pilot-link emerged, and none of
the USE flags seem to imply anything):

[ebuild   R   ] app-pda/pilot-link-0.12.3  USE="png python readline usb
(-bluetooth) -debug -java -perl -threads" 0 kB 
[ebuild     U ] mail-client/evolution-2.22.1.1 [2.22.1] USE="crypt dbus hal
mono pda spell ssl -debug -ipv6 -kerberos -krb4 -ldap -networkmanager -nntp
-profile" 0 kB 



Reproducible: Always

Steps to Reproduce:
1. emerge evolution with USE="pda"
2.
3.

Actual Results:  
checking for mkstemp... yes
checking for mkdtemp... yes
checking for isblank... yes
checking if ctime_r wants three arguments... no
checking for gethostbyname_r... yes
checking if gethostbyname_r wants five arguments... no
checking for gethostbyaddr_r... yes
checking if gethostbyaddr_r wants seven arguments... no
checking sys/statvfs.h usability... yes
checking sys/statvfs.h presence... yes
checking for sys/statvfs.h... yes
checking for statvfs... yes
checking sys/param.h usability... yes
checking sys/param.h presence... yes
checking for sys/param.h... yes
checking sys/mount.h usability... yes
checking sys/mount.h presence... yes
checking for sys/mount.h... yes
checking for statfs... yes
checking for GIT... yes
checking for A11Y... yes
checking for X11 XFree86 headers... yes
checking for OpenLDAP... no
checking for ldap_ntlm_bind... no
checking for SunLDAP... no
checking for pthread_create in -lpthread... yes
checking for regexec... yes
checking for GTKHTML... yes
checking for GNOME_PILOT... yes
checking if pilot-link handles UTF-8 conversions... no
configure: error: evolution requires pilot-link to have working UTF-8
conversion routines

*** This bug has been marked as a duplicate of bug 154453 ***

seemant, could you add config.log maybe this is glibc related after all :)

I see this is marked as a duplicate, but why is the duplicate marked as fixed
if it is still happening?

 * Messages for package mail-client/evolution-2.22.3.1:

 * 
 * ERROR: mail-client/evolution-2.22.3.1 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 2953:  Called gnome2_src_compile
 *             environment, line 2138:  Called gnome2_src_configure
 *             environment, line 2152:  Called econf 'src_compile'
'src_compile' '--without-kde-applnk-path' '--enable-plugins=experimental'
'--enable-nss' '--enable-smime' '--enable-ipv6' '--disable-mono'
'--disable-nntp' '--enable-pilot-conduits' '--disable-profiling'
'--with-openldap' '--with-krb5=/usr'
 *               ebuild.sh, line  513:  Called die
 * The specific snippet of code:
 *                      die "econf failed"
 *  The die message:
 *   econf failed
 * 
 * If you need support, post the topmost build error, and the call stack if
relevant.
 * A complete build log is located at
'/var/tmp/portage/mail-client/evolution-2.22.3.1/temp/build.log'.
 * The ebuild environment file is located at
'/var/tmp/portage/mail-client/evolution-2.22.3.1/temp/environment'.
 * 

Here is what is happening during configuration:

checking for ldap_ntlm_bind... yes
checking for pthread_create in -lpthread... yes
checking for regexec... yes
checking for GTKHTML... yes
checking for GNOME_PILOT... yes
checking if pilot-link handles UTF-8 conversions... no
configure: error: evolution requires pilot-link to have working UTF-8
conversion routines

Removed pda use flag to get around this.  I don't really even want evolution,
but it is apparently a dep for me to upgrade gnome...

thanks for not CCing me to a bug unless asked. I still don't see a config.log
so we are not going anywhere...

Created an attachment (id=165949) [details]
config.log with "pda" USE flag enabled

Attaching my config.log.

> thanks for not CCing me to a bug unless asked. I still don't see a config.log
> so we are not going anywhere...

Adding you as cc: to the issue isn't a breach of Bugzilla etiquette.

Don't know but it's just plain stupid to require the attention of one when
there's a whole team available for the job, especially considering I'm really
busy with other stuff. Don't get it wrong, drawing attention to a bug is good,
but please just don't ping one guy or your call might just get lost in the vast
TODO list we have.

Anyway, this looks like the interesting part of your log:

./conftest: error while loading shared libraries: libpisock.so.8: cannot open
shared object file: No such file or directory

missing pilot-link or a revdep-rebuild ?

@seemant, sorry for overtaking this bug and bothering you, I just hope this is
the same problem :)

grmbl, autoslap

(In reply to comment #7)
> Anyway, this looks like the interesting part of your log:
> 
> ./conftest: error while loading shared libraries: libpisock.so.8: cannot open
> shared object file: No such file or directory
> 
> missing pilot-link or a revdep-rebuild ?
> 
I had exactly the same problem, but revdep-rebuild did not help. The cause for
me was /usr/lib/libgpilotdconduit.so linked to libpisock.so.8 (while I had
.so.9 on my system).

Solved by emerging gnome-pilot and then evolution.

Not a real bug then, thanks for the follow up.