Problems compiling GPA

Markus Gerwinski markus@gerwinski.de
Fri Nov 22 17:46:02 2002


--mP3DRpeJDSE+ciuQ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Miguel Coca wrote:
> > So there's an internal conflict between gcc and cygwin... does anyone
> > already have experience with that one?
> No idea at all, sorry, but I suspect a configure problem. Maybe configure
> didn't find something that was already there, and now it's trying to compile
> a replacement?

We're suspecting now it's because our GPGME version was compiled for cygwin,
whereas we tried to make a "-mno-cygwin"-Compile (i.e. for MinGW) of GPA.
Now we're struggling to get GPGME compiled for MinGW.

> By the way, I'm sorry to inflict this on you :-) but since last night GPA
> requires GPGME 0.4.0 (or CVS HEAD, as it is currently unreleased). I had to
> do it, since we need the new API for gpgme_op_keygen, and when key
> signatures are implemented, they will be in 0.4.0.

Harrgh! I'm trying to compile it right now for Linux, but still I get this
warning of autogen.sh: "You should update your `aclocal.m4' by running aclocal"
... where running aclocal doesn't mean the least difference, and in the end I
get a buggy Makefile. Do you have an idea what's wrong here? (Or, maybe, an
already complete "configure" that could run on SuSE 8.0, too?)

I also got some problems with the last GPA I cvs'ed a week ago: In combination
with GnuPG 1.2, it refuses to fill my key list. I always get an error message:

  You have a secret key without the
  corresponding public key in your
  key ring. In order to use this key
  you will need to import the public
  key, too.

Anyway, this is _not_ true. When calling "gpg --list-secret-keys" and "gpg
--list-keys" from command line, it shows me one public key for every one of my
secret keys.

What's that again?

With cordial head-bangs,

  Markus

--mP3DRpeJDSE+ciuQ
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE93l636Sp5Kx1roGARAr48AJ4j+Rr6I/+tNxpTDWUAs2loG1q/EQCcCUUm
gQaf7qg74vL+5FiiTe6GDhA=
=Pi47
-----END PGP SIGNATURE-----

--mP3DRpeJDSE+ciuQ--