1836603 Members
2838 Online
110102 Solutions
New Discussion

Re: GnuPG2.0.9

 
Edward Browne
New Member

GnuPG2.0.9

I'm able to install gnuPG 1.4.9 with out any problems I'm attempting to install gnuPG 2.0.9 (OpenPGP)

gnupg 2.0.9 fails at the make with has anyone gotten 2.0.9 to make cleanly?
Error from make

gcc -DHAVE_CONFIG_H -I. -I.. -I../intl -I/usr/local/include -g -O2 -Wall -Wno-pointer-sign -Wpointer-arith -MT utf8conv.o -MD -MP -MF .deps/utf8conv.Tpo -c -o utf8conv.o utf8conv.c
utf8conv.c: In function 'native_to_utf8':
utf8conv.c:386: error: 'ICONV_CONST' undeclared (first use in this function)
utf8conv.c:386: error: (Each undeclared identifier is reported only once
utf8conv.c:386: error: for each function it appears in.)
utf8conv.c:386: error: expected ')' before 'char'
utf8conv.c: In function 'do_utf8_to_native':
utf8conv.c:652: error: 'ICONV_CONST' undeclared (first use in this function)
utf8conv.c:652: error: expected ')' before 'char'
gmake[2]: *** [utf8conv.o] Error 1
gmake[2]: Leaving directory `/usr/local/gnupg/gnupg-2.0.9/jnlib'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/usr/local/gnupg/gnupg-2.0.9'
gmake: *** [all] Error 2


I'm using GCC 4.2.3.

Posted to wrong fourm firt. I did try adding a
#define ICONV_CONST const to the config.h however it still fails to compile failing now at ld

ld: Unsatisfied symbol "libiconv_open" in file libjnlib.a[utf8conv.o]
ld: Unsatisfied symbol "libiconv_close" in file libjnlib.a[utf8conv.o]
ld: Unsatisfied symbol "libiconv" in file libjnlib.a[utf8conv.o]
3 errors.
collect2: ld returned 1 exit status
gmake[2]: *** [t-stringhelp] Error 1
gmake[2]: Leaving directory `/usr/local/gnupg/gnupg-2.0.9/jnlib'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/usr/local/gnupg/gnupg-2.0.9'
gmake: *** [all] Error 2


There was no metion of this lib in the requirements.
1 REPLY 1
Steven Schweda
Honored Contributor

Re: GnuPG2.0.9

http://www.gnu.org/software/libiconv/

The complaint about ICONV_CONST was probably
a clue.

> There was no metion of this lib in the
> requirements.

Trust no one, I always say. When you always
have every bit of GNU stuff installed on your
systems, it's a bother to puzzle out exactly
which bits are needed for any particular
project.