GnuPG v2.0.8 on windows 32 bit platform

Tom Pegios tomp at idirect.com
Fri Jan 4 18:53:56 CET 2008


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Has anyone that has compiled GnuPG v2.0.8 for Windows(32) run into the
following problem as I'm not sure if I'm doing something wrong

Running make check for gpg2 shows ALL tests pass BUT make check fails on
 the following libraries.
- - - ------------------------
in libksba-1.0.2

make[2]: Entering directory `/src/v2/libksba-1.0.2/tests'
/bin/sh ../libtool --tag=CC   --mode=link gcc -I/usr/local/include -g
- - - -O2 -Wall-Wcast-align -Wshadow -Wstrict-prototypes -Wpointer-arith
- - - -Wno-pointer-sign   -o cert-basic.exe cert-basic.o ../src/libksba.la
- - - -L/usr/local/lib -lgpg-errorgcc -I/usr/local/include -g -O2 -Wall
- - - -Wcast-align -Wshadow -Wstrict-prototypes -Wpointer-arith
- - - -Wno-pointer-sign -o .libs/cert-basic.exe cert-basic.o  ../src/.
libs/libksba.dll.a -L/usr/local/lib /usr/local/lib/libgpg-error.dll.a
- - - -L/usr/local/lib
cert-basic.o: In function `one_file':
d:\M-SYS\src\v2\libksba-1.0.2\tests/cert-basic.c:591: undefined
reference to `__
ksba_keyinfo_from_sexp'
d:\M-SYS\src\v2\libksba-1.0.2\tests/cert-basic.c:602: undefined
reference to `__
ksba_keyinfo_to_sexp'
d:\M-SYS\src\v2\libksba-1.0.2\tests/cert-basic.c:615: undefined
reference to `__
ksba_keyinfo_from_sexp'
collect2: ld returned 1 exit status

- - - ----------------------------------------
in libgcrypt-1.4.0

15 of 15 tests failed
Please report to bug-libgcrypt at gnupg.org
========================================
make[2]: *** [check-TESTS] Error 1
make[2]: Leaving directory `/src/v2/libgcrypt-1.4.0/tests'
make[1]: *** [check-am] Error 2

- - - -----------------------------
 in libgpg-error-1.6

make  check-TESTS
make[2]: Entering directory `/src/v2/libgpg-error-1.6/tests'
FAIL: t-strerror.exe
FAIL: t-syserror.exe
====================================
2 of 2 tests failed


GPG2 seems to work properly but with the libraries falling the above
tests I'm sure if I an trust GPG2 to work properly. anyone have any
ideas ???

Tom

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.8 (MingW32)

iEYEAREIAAYFAkd+crMACgkQxDTq4V42xe555QCdGC1lcvWcFORQVIAdgQVA9w/l
HhUAn00UFt4lqCoOIkFSy9KemDY8ZSqP
=0aDl
-----END PGP SIGNATURE-----




More information about the Gnupg-devel mailing list