[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Pan-devel] testing branch as of 3896f1cae: build failure without gn

From: Heinrich Mueller
Subject: Re: [Pan-devel] testing branch as of 3896f1cae: build failure without gnome-keyring
Date: Mon, 12 Dec 2011 10:26:41 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111108 Thunderbird/8.0

Am 11.12.2011 20:37, schrieb Duncan:
No gnome, so no gnome-keyring, here.  It'd be kgpg or kwallet, here.

During configure:

checking for OPENSSL... yes
checking for LIBNOTIFY... no
checking for LIBGSASL... no
checking for LIBGNOME_KEYRING_1... no
checking for gpgme-config... /usr/bin/gpgme-config
checking for GPGME - version>= 1.3.0... yes

During make:

Making all in data
make[3]: Entering directory `/tmp/portage/net-nntp/pan-9999/work/pan-9999/


In file included from ../../pan/data/cert-store.h:35:0,
                  from ../../pan/usenet-utils/ssl-utils.h:32,
../../pan/data/data.h:39:50: fatal error: gnome-keyring-1/gnome-keyring-
memory.h: No such file or directory
compilation terminated.
make[3]: *** [cert-store.o] Error 1
make[3]: *** Waiting for unfinished jobs....
In file included from
data.h:39:50: fatal error: gnome-keyring-1/gnome-keyring-memory.h: No
such file or directory

configure set no libgnome_keyring, so why is it still trying to use it?


How do I hard-(en|dis)able the gnome-keyring dependency?  I don't see a
configure switch listed for it.

And while we're at it, how do I hard-(en|dis)able libnotify?

(Gentoo people don't tend to appreciate "automagic" dependencies as they
tend to cause problems when a package not tracked in the dependencies is
removed, breaking anything that "automagically" depended on it.  Thus,
hard enable/disable is required.)

And confirming...

You deliberately bumped the gmime dependency to 2.6, correct?  The only
thing I have depending on gmime here is pan, and I had it set to the 2.4
slot (gentoo's method of allowing multiple versions side-by-side).  I had
to change it to 2.6 as that's what configure was testing for now.  Not a
problem, at least for me.  Just confirming that you bumped the dep

Hey Duncan. I'll change that for you to compile again, I just didn't
check all the possibilities yet.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]