bug-gnubg
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-gnubg] Problems compiling


From: Sander van Rijnswou
Subject: Re: [Bug-gnubg] Problems compiling
Date: Sat, 03 Aug 2002 13:33:38 +0200

Hello,

After the advice of Joern I had some succes compiling the later versions
of gnbg. 

For the snapshot gnubg-020727.tar.gz it worked by
saying configure --without-guile. This is a bit strange since guile
1.4.1 is installed and found by configure.
(This is the error I get when I leave out --without-guile)

gcc -c -DLOCALEDIR=\"/usr/local/share/locale\"
-DLOCALE_ALIAS_PATH=\"/usr/local/share/locale\"
-DLIBDIR=\"/usr/local/lib\" -DHAVE_CONFIG_H -I.. -I. -I../intl  -g -O2 
l10nflist.c
l10nflist.c:65: warning: static declaration for `stpcpy' follows
non-static
l10nflist.c:396: parse error before `__extension__'
l10nflist.c:399: parse error before `{'             

Unfortunately I had no succes with the CVS version. 
Whatever configure options I try. Configure will always complain that 


sed: can't read ./intl/po2tbl.sed.in: No such file or directory         


After which I get all kinds of missing symbols


gnubg > make
cd . && autoheader
configure.in:201: AC_TRY_COMPILE was called before AC_ISC_POSIX
configure.in:201: AC_TRY_RUN was called before AC_ISC_POSIX
/usr/bin/autoheader: Symbol `ENABLE_NLS' is not covered by
/usr/share/autoconf/acconfig.h ./acconfig.h
/usr/bin/autoheader: Symbol `HAVE_CATGETS' is not covered by
/usr/share/autoconf/acconfig.h ./acconfig.h
/usr/bin/autoheader: Symbol `HAVE_GETTEXT' is not covered by
/usr/share/autoconf/acconfig.h ./acconfig.h
/usr/bin/autoheader: Symbol `HAVE_LC_MESSAGES' is not covered by
/usr/share/autoconf/acconfig.h ./acconfig.h
/usr/bin/autoheader: Symbol `HAVE_STPCPY' is not covered by
/usr/share/autoconf/acconfig.h ./acconfig.h
make: *** [stamp-h.in] Error 1
address@hidden:~/project/gnubg-cvs/gnubg >
 
 
do others have the file /intl/po2tbl.sed.in ?? Or is configure somehow
supposed to make it?
                                          


Thanks,

Sander.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]