[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 84970] gpgme compile error message is unclear
From:       David Faure <faure () kde ! org>
Date:       2004-07-12 11:32:22
Message-ID: 20040712113222.25760.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
      
http://bugs.kde.org/show_bug.cgi?id=84970      




------- Additional Comments From faure kde org  2004-07-12 13:32 -------
On Sunday 11 July 2004 23:41, Tom Albers wrote:
> Well, I just took the path here and put it in the --with-gpgme-prefix thing. That \
> did not work. /usr/local/bin did not work, it seems you have to use /usr/local/ as \
> a path. 
> Could you make the error as in:
> ---
> Consider downloading gpgme >= 0.4.5 from ftp://ftp.gnupg.org/gcrypt/alpha/gpgme
> if you have installed it, please give the base path, for example if gpg is located \
> at /usr/local/bin/gpg please use the --with-gpgme-prefix=/usr/local/ option.

You're confusing gpg and gpgme.
gpg is the binary
gpgme is a library.
gpgme looks for gpg on configure (as you saw). You can tell it where to find it if \
needed.

kdepim's configure looks for gpgme (the library) and ships its own if you don't have \
it. So when you install gpgme into some prefix, you have to give that prefix to \
--with-gpgme-prefix. By default the prefix is /usr/local, just like most other free \
software source packages out there. This has nothing to do with where gpg itself is \
located.

Note also that the warning from configure said "A or B" but you did A _and_ B :)
Wasn't gpgme found in /usr/local automatically, without passing any \
--with-gpgme-prefix option? If not, then that would be the bug, I guess.


[prev in list] [next in list] [prev in thread] [next in thread]