On Mon, Sep 22, 2003 at 02:51:03PM +0200, Han-Wen Nienhuys wrote: > [EMAIL PROTECTED] writes: > > > > I get the same error with SuSE-8.2 and lilypond 1.8.1. > > > > If I'm right, the problem is that the configure script concludes that > > snprintf is not provided by stdio.h although it is. If I change in > > config.h the setting for HAVE_SNPRINTF and HAVE_VSNPRINTF, the file > > compiles. (I get another error in the directory lily, but I assume that this > > is not related to this problem.) > > > > Since I always avoided function pointers, I cannot judge whether the test in > > configure should work. Here is the exerpt from config.h: > > We haven't been able to duplicate this problem (with Debian). Can you > file a bugreport with SuSE please.
Which version of Debian and which compiler? SuSE 8.2 comes with g++ 3.3 autoconf 2.57 glibc 2.3.2 If I'm correct, Debian unstable provides the same packages. Furthermore I think that the problem is how the linker handles exceptions. Anyway, following the suggestion of http://mail.gnu.org/archive/html/bug-autoconf/2003-01/msg00004.html to switch from AC_CHECK_FUNCS to AC_CHECK_DECLS should solve the problem for snprintf and vsnprintf. Finally, I was able to build lilypond 1.8.2 on SuSE 8.2 as follows: - run configure - run lexer-gcc-3.1.sh - reconfigure as written by lexer-gcc-3.1.sh - run lexer-gcc-3.1.sh - change HAVE_SNPRINTF and HAVE_VSNPRINTF from 0 to 1 in config.h - run make - add a semicolon in line 1882 of lily/parser.yy: | STRING { $$ = $1; } - run make Best regards Thomas -- http://www.thomas.willhalm.de/ _______________________________________________ Bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond
