Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: GnuPG: users

GPG 2.1 beta compilation error

 

 

GnuPG users RSS feed   Index | Next | Previous | View Threaded


ben at adversary

Jul 25, 2012, 8:50 PM

Post #1 of 5 (199 views)
Permalink
GPG 2.1 beta compilation error

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hello,
I've just tried compiling GPG 2.1.0 beta 3 on a CentOS/RHEL 5
box. I'm installing in and to /usr/local with all the dependencies in
the same location.

I configured it with the following options:

./configure --enable-symcryptrun --enable-gpgtar --enable-selinux-support

The configuration process was fine, but when I tried to make it I
received this error:

passphrase.c: In function ‘passphrase_to_dek_ext’:
passphrase.c:584: warning: implicit declaration of function
‘gcry_kdf_derive’
passphrase.c:585: error: ‘GCRY_KDF_ITERSALTED_S2K’ undeclared (first
use in this function)
passphrase.c:585: error: (Each undeclared identifier is reported only once
passphrase.c:585: error: for each function it appears in.)
passphrase.c:586: error: ‘GCRY_KDF_SALTED_S2K’ undeclared (first use
in this function)
passphrase.c:587: error: ‘GCRY_KDF_SIMPLE_S2K’ undeclared (first use
in this function)
make[2]: *** [passphrase.o] Error 1
make[2]: Leaving directory `/usr/local/src/gnupg-2.1.0beta3/g10'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/local/src/gnupg-2.1.0beta3'
make: *** [all] Error 2

Is this a bug or do I need to fix something?


Regards,
Ben

-----BEGIN PGP SIGNATURE-----

iEYEAREKAAYFAlAQvoEACgkQNxrFv6BK4xMAmwCgij5wCTBXkJpQ71uEpVF1Y86b
mU8AoJ+AYZsJ5Z6oD5N+tcmCsf+xxTV1
=jAZe
-----END PGP SIGNATURE-----


_______________________________________________
Gnupg-users mailing list
Gnupg-users [at] gnupg
http://lists.gnupg.org/mailman/listinfo/gnupg-users


ben at adversary

Jul 25, 2012, 9:10 PM

Post #2 of 5 (197 views)
Permalink
Re: GPG 2.1 beta compilation error [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 26/07/12 1:50 PM, Ben McGinnes wrote:
> Hello, I've just tried compiling GPG 2.1.0 beta 3 on a CentOS/RHEL
> 5 box. I'm installing in and to /usr/local with all the
> dependencies in the same location.
>
> I configured it with the following options:
>
> ./configure --enable-symcryptrun --enable-gpgtar
> --enable-selinux-support
>
> The configuration process was fine, but when I tried to make it I
> received this error:
>
> passphrase.c: In function ‘passphrase_to_dek_ext’:
> passphrase.c:584: warning: implicit declaration of function
> ‘gcry_kdf_derive’ passphrase.c:585: error:
> ‘GCRY_KDF_ITERSALTED_S2K’ undeclared (first use in this function)
> passphrase.c:585: error: (Each undeclared identifier is reported
> only once passphrase.c:585: error: for each function it appears
> in.) passphrase.c:586: error: ‘GCRY_KDF_SALTED_S2K’ undeclared
> (first use in this function) passphrase.c:587: error:
> ‘GCRY_KDF_SIMPLE_S2K’ undeclared (first use in this function)
> make[2]: *** [passphrase.o] Error 1 make[2]: Leaving directory
> `/usr/local/src/gnupg-2.1.0beta3/g10' make[1]: *** [all-recursive]
> Error 1 make[1]: Leaving directory
> `/usr/local/src/gnupg-2.1.0beta3' make: *** [all] Error 2
>
> Is this a bug or do I need to fix something?

I just tried it without passing any options to configure and received
this error when running make:

tatus.c:25:26: error: status-codes.h: No such file or directory
status.c: In function ‘get_status_string’:
status.c:32: warning: implicit declaration of function
‘statusstr_msgidxof’
status.c:36: error: ‘statusstr_msgstr’ undeclared (first use in this
function)
status.c:36: error: (Each undeclared identifier is reported only once
status.c:36: error: for each function it appears in.)
status.c:36: error: ‘statusstr_msgidx’ undeclared (first use in this
function)
make[3]: *** [libcommon_a-status.o] Error 1
make[3]: Leaving directory `/usr/local/src/gnupg-2.1.0beta3/common'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/usr/local/src/gnupg-2.1.0beta3/common'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/local/src/gnupg-2.1.0beta3'
make: *** [all] Error 2


Regards,
Ben

-----BEGIN PGP SIGNATURE-----

iEYEAREKAAYFAlAQw1EACgkQNxrFv6BK4xP31ACg9lbUi1cwmY0K/38K0F5aQNAX
9L0AoJgqWpMnGTwops/uAj3fR3SQKdNT
=xAXU
-----END PGP SIGNATURE-----


_______________________________________________
Gnupg-users mailing list
Gnupg-users [at] gnupg
http://lists.gnupg.org/mailman/listinfo/gnupg-users


wk at gnupg

Jul 26, 2012, 12:25 AM

Post #3 of 5 (191 views)
Permalink
Re: GPG 2.1 beta compilation error [In reply to]

On Thu, 26 Jul 2012 05:50, ben [at] adversary said:

> passphrase.c:585: error: ‘GCRY_KDF_ITERSALTED_S2K’ undeclared (first
> use in this function)

You need at least Libgcrypt 1.5.0. However, configure should have
detected this. Thus the build process accidentally picked up another
gcrypt.h than the configure test. Check the config.log and an actual cc
invocation line to figure out what went wrong.


Salam-Shalom,

Werner

--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.


_______________________________________________
Gnupg-users mailing list
Gnupg-users [at] gnupg
http://lists.gnupg.org/mailman/listinfo/gnupg-users


ben at adversary

Jul 26, 2012, 12:54 AM

Post #4 of 5 (190 views)
Permalink
Re: GPG 2.1 beta compilation error [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 26/07/12 5:25 PM, Werner Koch wrote:
> On Thu, 26 Jul 2012 05:50, ben [at] adversary said:
>
>> passphrase.c:585: error: ‘GCRY_KDF_ITERSALTED_S2K’ undeclared
>> (first use in this function)
>
> You need at least Libgcrypt 1.5.0. However, configure should have
> detected this. Thus the build process accidentally picked up
> another gcrypt.h than the configure test. Check the config.log
> and an actual cc invocation line to figure out what went wrong.

I compiled libgcrypt-1.5.0-beta1 in /usr/local, but there's probably
another version elsewhere. Should I be using the following flags?

--with-libgpg-error-prefix=PFX
--with-libgcrypt-prefix=PFX
--with-libassuan-prefix=PFX
--with-ksba-prefix=PFX
--with-pth-prefix=PFX

Any or all of them? Should I just use "/usr/local" with them or full
paths to binaries?


Regards,
Ben

-----BEGIN PGP SIGNATURE-----

iEYEAREKAAYFAlAQ97UACgkQNxrFv6BK4xOtJQCZAaAUWECljnBiDF8SVuoXg09N
6LMAn1x8uFO/m9SR/Owe4fygZKUfVU6N
=pS5T
-----END PGP SIGNATURE-----


_______________________________________________
Gnupg-users mailing list
Gnupg-users [at] gnupg
http://lists.gnupg.org/mailman/listinfo/gnupg-users


ben at adversary

Jul 26, 2012, 3:40 AM

Post #5 of 5 (197 views)
Permalink
Re: GPG 2.1 beta compilation error [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 26/07/12 5:25 PM, Werner Koch wrote:
> On Thu, 26 Jul 2012 05:50, ben [at] adversary said:
>
>> passphrase.c:585: error: ‘GCRY_KDF_ITERSALTED_S2K’ undeclared
>> (first use in this function)
>
> You need at least Libgcrypt 1.5.0. However, configure should have
> detected this. Thus the build process accidentally picked up
> another gcrypt.h than the configure test. Check the config.log and
> an actual cc invocation line to figure out what went wrong.

Okay, I tried it again with all the paths set to /usr/local and the
following appeared in the configure log:

configure: checking for libraries
checking for gpg-error-config... /usr/local/bin/gpg-error-config
checking for GPG Error - version >= 1.10... yes (1.10)
checking for libgcrypt-config... /usr/local/bin/libgcrypt-config
checking for LIBGCRYPT - version >= 1.5.0... yes (1.5.0-beta1)
checking LIBGCRYPT API version... okay
checking for libassuan-config... /usr/local/bin/libassuan-config
checking for LIBASSUAN - version >= 2.0.3... yes (2.0.3)
checking LIBASSUAN API version... okay
checking for ksba-config... /usr/local/bin/ksba-config
checking for KSBA - version >= 1.2.0... yes (1.2.0)
checking KSBA API version... okay
checking for usb_bulk_write in -lusb... yes
checking for usb_create_match... no
checking for library containing dlopen... -ldl
checking for encfs... /usr/bin/encfs
checking for fusermount... /bin/fusermount
checking for openpty in -lutil... yes
checking for shred... /usr/bin/shred
checking for pth-config... /usr/local/bin/pth-config
checking for PTH - version >= 1.3.7... yes
checking whether PTH installation is sane... yes

You'd think that everything would be fine, but I still ended up with
this:

status.c:25:26: error: status-codes.h: No such file or directory
status.c: In function ‘get_status_string’:
status.c:32: warning: implicit declaration of function
‘statusstr_msgidxof’
status.c:36: error: ‘statusstr_msgstr’ undeclared (first use in this
function)
status.c:36: error: (Each undeclared identifier is reported only once
status.c:36: error: for each function it appears in.)
status.c:36: error: ‘statusstr_msgidx’ undeclared (first use in this
function)
make[3]: *** [libcommon_a-status.o] Error 1
make[3]: Leaving directory `/usr/local/src/gnupg-2.1.0beta3/common'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/usr/local/src/gnupg-2.1.0beta3/common'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/local/src/gnupg-2.1.0beta3'
make: *** [all] Error 2

I've got the entire output of configure and make (up until the moment
it hit that error), but it's about 25Kb of text and I'm unsure about
sending the whole lot through to the list. I can send you the lot
directly if you like.


Regards,
Ben

-----BEGIN PGP SIGNATURE-----

iEYEAREKAAYFAlARHo8ACgkQNxrFv6BK4xPemACZAeKtvn5WON/zse1RaTUEyz5R
K+QAniOOnMWtngPfCOEiz+JO3Jy0smbz
=IzNH
-----END PGP SIGNATURE-----


_______________________________________________
Gnupg-users mailing list
Gnupg-users [at] gnupg
http://lists.gnupg.org/mailman/listinfo/gnupg-users

GnuPG users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.