Re: Build failure with today's svn

Peter Wainwright <[email protected]>
Newsgroups gmane.comp.debugging.ddd.general
Message-ID <[email protected]>
On Mon, 2006-12-18 at 14:28 -0500, David Ronis wrote:
> I just tried to build svn version 6836 on an i686-linux box using
> gcc-4.1.1.  The last version I built was:  GNU DDD 3.3.12-test2
> (i686-pc-linux-gnu).  
> 
> I ran ./configure; make
> 
> and after a while got:
> 
> make[2]: Entering directory `/home/ronis/Project/notar/ddd/ddd'
> if /usr/bin/g++ -DHAVE_CONFIG_H -I. -I. -I.  -I./..
> -isystem /usr/X11R6/include   -O3  -Wall -W -Wwrite-strings
> -march=prescott -ffast-math -funroll-loops -fomit-frame-pointer
> -trigraphs  -MT VSLRead.o -MD -MP -MF ".deps/VSLRead.Tpo" -c -o
> VSLRead.o VSLRead.C; \
>         then mv -f ".deps/VSLRead.Tpo" ".deps/VSLRead.Po"; else rm -f
> ".deps/VSLRead.Tpo"; exit 1; fi
> y.tab.c:343: error: expected unqualified-id before 'delete'
> lex.vsl.c:1550: warning: 'void vslunput(int, char*)' defined but not
> used
> make[2]: *** [VSLRead.o] Error 1
> 

This looks like the same bug as
http://lists.gnu.org/archive/html/ddd/2006-10/msg00006.html. There would
be no problems with a release tarball, because the parser is prebuilt
there.  In the SVN version it is built on your own system using a parser
generator (yacc or bison).  It looks like some versions of bison cause
problems but I have not had time to make a fix.

Peter

> David
> 
> 
> 
> 
> _______________________________________________
> Ddd mailing list
> [email protected]
> http://lists.gnu.org/mailman/listinfo/ddd

_______________________________________________
Ddd mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/ddd
signature.asc (application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBFiX0yZlbFk+UVjRoRAqmgAKCzpsMtaunjRX3I5EuyKU/3QF+HwgCfeqXf
H/4NR8IHYUKOeYIJJWgYKi4=
=9v7z
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.