bug-bison
[Top][All Lists]
Advanced

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

Re: type clash on default action: <NONE> != <>


From: Paul Eggert
Subject: Re: type clash on default action: <NONE> != <>
Date: Sat, 7 Dec 2002 23:22:14 -0800 (PST)

> Date: Sun, 8 Dec 2002 01:40:23 +0100 (CET)
> From: =?iso-8859-2?Q?Martin_MOKREJ=A9?= <address@hidden>

>   thanks for the patch. I've tried bison 1.75c on Tru64Unix 5.1A box and
> have some problems compiling kerberos4:
> 
> $ bison -y -d  `test -f 'parse.y' || echo './'`parse.y

Which version of kerberos4 are you compiling?
<ftp://ftp.pdc.kth.se/pub/krb/src/krb4-1.2.1.tar.gz>
contains two "parse.y" files; which one is causing you problems?

>    5 skel_lex() ["scan-skel.c":73, 0x1200433b8]

Weird.  I assume that was really "scan-skel.l", not "scan-skel.c",
as line 73 makes sense only for scan-skel.l.

I cannot reproduce the bug on my 64-bit SPARC host.

Can you please save the m4's input and output using the following
trick?  Please substitute the location of your copy of the GNU m4
executable for "/opt/sfw/bin/gm4".

   $ cat >m4 <<'EOF'
   #! /bin/sh
   cat >m4.input
   /opt/sfw/bin/gm4 "$@" <m4.input >m4.output
   cat <m4.output
   EOF
   $ chmod a+x m4
   $ M4=`pwd`/m4 bison -y -d ./parse.y

When you're done, you should have files "m4.input" and "m4.output" in
your directory; please email their contents to bug-bison.



reply via email to

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