OPKG - configure: error: GPGME 1.0.0 or later needed

[GoogleCodeExporter]

1 - Cross compiling for mini2440 (arm-linux-gcc)
2 - gpgme 1.3.1 installed (cross-compiled, with all libraries)
3 - make opkg 0.1.8
----------------------------------------------------------

My aim is OPKG 0.1.8 that needs GPGME (my version 1.3.1).
I'm crosscompiling, and I also try these ** opts

**

--with-gpgme-config=... --with-gpgme=...
--with-gpg=... --with-gpg-error-prefix=... --with-libgcrypt-prefix=...
--with-libassuan-prefix=... --with-gpgsm=... --with-ksba-prefix=...
--with-gpgconf=...

( where ... = "/my/os/absoulte/path/to/usr" )
( the executable of gpgme-config is in .../bin/ and it works! )

*
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... no
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking pkg-config is at least version 0.20... yes
checking for CURL... yes
checking if openssl is available... checking for OPENSSL... yes
yes
checking for gpgme-config... failed
configure: error: GPGME 1.0.0 or later needed

Any suggestion?

Thanks in advance

Original issue reported on code.google.com by marco_ca...@libero.it on 4 Nov 2011 at 10:20

[GoogleCodeExporter]

PS.
configure...

unrecognized options: --with-gpgme-config ((--disable-gtk-doc --diasble-nls))

Original comment by marco_ca...@libero.it on 4 Nov 2011 at 10:42

[GoogleCodeExporter]

I'm trying to tidy up the issue tracker a bit. This report is fairly old. If 
it's still relevant could you post the exact configure command line which 
causes the error? I think the --with-PACKAGE=ARG are only intended to have 
"yes" or "no" given as arguments, not paths.

If there's no reply within a month I'll close this.

Original comment by paul.betafive on 3 Aug 2013 at 10:01

[GoogleCodeExporter]

I don't have enough info to reproduce this bug. I'd guess that the gpgme-config 
program needs to be on your PATH and wasn't.

Original comment by paul.betafive on 28 Sep 2013 at 1:02

• Changed state: Invalid