Re: [SPAM] [GNU Bison 2.3] testsuite: 155 failed

Hi Joel,

* Joel E. Denny <jdenny <at> ces.clemson.edu> [070128 21:39]:
> On Sun, 28 Jan 2007, Christian Kellermann wrote:
> 
> > I am in the progress of updating OpenBSD's GNU bison port to 2.3.
> > The compilation works without errors. During the regression tests,
> > there are failures. I have attached the testsuite.log. If there is
> > anymore information I can provide I will happily do so.
> 
> Thanks for the report.
Sorry for my late reply. Please find my results below.

> Please try the following commands from the root of your Bison build:
> What output do you get?
>   cd tests
>   ./testsuite -d 155

[Banners omitted]
155: Incorrect lookahead during nondeterministic GLRFAILED (glr-regression.at:1405)

>   cd testsuite.dir/155
>   ../../bison -o glr-regr14.c glr-regr14.y 

glr-regr14.y: conflicts: 3 reduce/reduce

>   cc glr-regr14.c

glr-regr14.y:38: warning: `union YYSTYPE' declared inside parameter list
glr-regr14.y:38: warning: its scope is only this definition or

Re: [SPAM] [GNU Bison 2.3] testsuite: 155 failed

Christian Kellermann <Christian.Kellermann <at> nefkom.net> writes:

>>   cc glr-regr14.c
>
> glr-regr14.y:38: warning: `union YYSTYPE' declared inside parameter list

That's odd; there should be a union YYSTYPE defined.  What
is the output of the following commands, on the original
glr-regr14.c file without your editing it?

   cat glr-regr14.c

   cc -E glr-regr14.c

Re: [SPAM] [GNU Bison 2.3] testsuite: 155 failed

Hi Paul,

* Paul Eggert <eggert <at> CS.UCLA.EDU> [070201 23:02]:
> Christian Kellermann <Christian.Kellermann <at> nefkom.net> writes:
> 
> >>   cc glr-regr14.c
> >
> > glr-regr14.y:38: warning: `union YYSTYPE' declared inside parameter list
> 
> That's odd; there should be a union YYSTYPE defined.  What
> is the output of the following commands, on the original
> glr-regr14.c file without your editing it?
> 
>    cat glr-regr14.c
I have attached the file below.

> 
>    cc -E glr-regr14.c
dito.

I have double checked the included patches for openbsd (by the old
maintainer. These just include path corrections to our build
environment and are irrelevant to this issue)

I hope I could help you a litte. I will provide further information
as needed.

Cheers,

Christian

recent Gnulib changes break Bison

I just did a fresh checkout of Bison.  Attached is the output of make, 
which failed.  I haven't been following the Gnulib mailing lists lately, 
and I don't have time to debug right now.  Maybe one of our Gnulib experts 
can fix this.

Making all in build-aux
make[1]: Entering directory `/home/jdenny/bison/build-aux'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/home/jdenny/bison/build-aux'
Making all in po
make[1]: Entering directory `/home/jdenny/bison/po'
make bison.pot-update
make[2]: Entering directory `/home/jdenny/bison/po'
sed -e '/^#/d' remove-potcdate.sin > t-remove-potcdate.sed
mv t-remove-potcdate.sed remove-potcdate.sed
if test -n 'bug-bison <at> gnu.org' || test 'bug-bison <at> gnu.org' = ' <at> 'PACKAGE_BUGREPORT' <at> '; then \
  msgid_bugs_address='bug-bison <at> gnu.org'; \
else \
  msgid_bugs_address='bug-bison <at> gnu.org'; \
fi; \
/usr/local/bin/xgettext --default-domain=bison --directory=.. \
  --add-comments=TRANSLATORS: --keyword=_ --keyword=N_ --flag=_:1:pass-c-format --flag=N_:1:pass-c-format --flag=error:3:c-format --flag=error_at_line:5:c-format --from-code=UTF-8 --flag=asprintf:2:c-format --flag=complain:1:c-format --flag=complain_at:2:c-format --flag=fatal:1:c-format --flag=fatal_at:2:c-format --flag=warn:1:c-format  --flag=warn_at:2:c-format --flag=unexpected_end:2:c-format ${end_of_xgettext_options+} \
  --files-from=./POTFILES.in \
  --copyright-holder='Free Software Foundation, Inc.' \
  --msgid-bugs-address="$msgid_bugs_address"
/usr/local/bin/xgettext: warning: file `src/parse-gram.y' extension `y' is unknown; will try C
/usr/local/bin/xgettext: warning: file `src/scan-code.l' extension `l' is unknown; will try C
/usr/local/bin/xgettext: warning: file `src/scan-gram.l' extension `l' is unknown; will try C
test ! -f bison.po || { \
  if test -f ./bison.pot; then \

Re: [SPAM] [GNU Bison 2.3] testsuite: 155 failed

Here is the only difference between what you sent and what I get with
the same test.

diff -prubw 155/glr-regr14.c 155-bad/glr-regr14.c
--- 155/glr-regr14.c	2007-02-01 13:58:12.000000000 -0800
+++ 155-bad/glr-regr14.c	2007-02-03 16:45:21.000000000 -0800
@@ -69,10 +69,10 @@

 
 #if ! defined YYSTYPE && ! defined YYSTYPE_IS_DECLARED
-typedef union YYSTYPE 
+typedef union 
 #line 31 "glr-regr14.y"
 { char value; }
-/* Line 203 of glr.c.  */
+/* Line 204 of glr.c.  */
 #line 77 "glr-regr14.c"
 	YYSTYPE;
 # define YYSTYPE_IS_DECLARED 1

This difference does explain the symptoms.  But now we need to figure
out why you're getting the difference.

The relevant line in glr.c looks like this:

[typedef union m4_bregexp(b4_stype, [^{], [YYSTYPE ])

So one possibility is that your version of 'm4' mishandles
a regular expression of the form "^{".  Perhaps it thinks that
the "{" is part of regular expression punctuation?

Re: recent Gnulib changes break Bison

On Thu, 1 Feb 2007, Joel E. Denny wrote:

> I just did a fresh checkout of Bison.  Attached is the output of make, 
> which failed.  I haven't been following the Gnulib mailing lists lately, 
> and I don't have time to debug right now.  Maybe one of our Gnulib experts 
> can fix this.

The mailing list took its time to deliver this.  Anyway, Gnulib seems to 
have been fixed in the meantime.

Re: recent Gnulib changes break Bison

I installed the following to fix this:

2007-02-03  Paul Eggert  <eggert <at> cs.ucla.edu>

	* .cvsignore: Add javacomp.sh, javaexec.sh.  Is this really
	the right spot for these files?
	* bootstrap.conf (gnulib_modules): Add c-strcase.
	* lib/.cvsignore: Add c-ctype.c c-ctype.h, c-strcasecomp.c,
	c-strncasecmp.c.
	* src/getargs.c: Include c-strcase.h.
	(language_argmatch): Use c_strcasecmp rather than strcasecmp,
	to avoid unspecified behavior.

Index: .cvsignore
===================================================================
RCS file: /cvsroot/bison/bison/.cvsignore,v
retrieving revision 1.25
diff -u -p -r1.25 .cvsignore
--- .cvsignore	20 Sep 2006 20:22:24 -0000	1.25
+++ .cvsignore	4 Feb 2007 07:18:55 -0000
@@ -20,6 +20,8 @@ config.status
 configure
 configure.lineno
 conftest*
+javacomp.sh
+javaexec.sh
 patches
 releases
 stamp-h*
Index: bootstrap.conf

Java-related Bison tests all fail

This is on Debian stable, with GCC 4.1.1 installed by hand, when
testing the latest Bison CVS.  Any clues as to what I'm doing wrong?
It could be a misinstallation of GCC, but if I do it wrong others are
likely too.

662-penguin $ ./testsuite -v -d 177 178 179 180
## --------------------------- ##
## GNU Bison 2.3a+ test suite. ##
## --------------------------- ##

Java Calculator.

177. java.at:308: testing ...
./java.at:308: bison -o Calc.java Calc.y
./java.at:308: test -n "$CONF_JAVA$CONF_JAVAC" || exit 77
./java.at:308: $SHELL ../../../javacomp.sh Calc.java
stderr:
stdout:
./java.at:308:  $SHELL ../../../javaexec.sh Calc < input
stderr:
./java.at:308:  $SHELL ../../../javaexec.sh Calc < input
stderr:
1: syntax error
Exception in thread "main" java.lang.IllegalAccessError: Calc: Calc$Stack.height
   at Calc.parse(Calc.java:731)
   at Calc.main(Calc.java:1081)
./java.at:308: exit code was 1, expected 0
177. java.at:308:  FAILED (java.at:308)

178. java.at:308: testing ...

Re: [SPAM] [GNU Bison 2.3] testsuite: 155 failed

* Paul Eggert <eggert <at> CS.UCLA.EDU> [070204 02:08]:
> Here is the only difference between what you sent and what I get with
> the same test.
> Which version of m4 are you using?  What is the output of "m4 --version"?
> Did you build this m4, or did someone else build it for you?
> 
> What happens when you try regexp(`{abc', `^{', `foo') with your m4?
> Here's what happens with mine (m4 1.4.8):
> 
> $ m4
> regexp(`{abc', `^{', `foo')
> foo

I am using the OpenBSD package for m4 versioned with 1.4.4
This m4 does not have a --version switch.

But I get the same result with your example above.

I will have a closer look into the build system later and watch out
for possible changes to that behaviour. Unfortunately I am not
familiar with m4, so I may miss something.

I would be grateful for further assistance from your side.

Thanks for your help,

Christian

--

-- 
You may use my gpg key for replies:

Re: [SPAM] [GNU Bison 2.3] testsuite: 155 failed

Christian Kellermann <Christian.Kellermann <at> nefkom.net> writes:

> I am using the OpenBSD package for m4 versioned with 1.4.4
> This m4 does not have a --version switch.

Now you've lost me.  OpenBSD m4 has a version number that is the same
as GNU m4's version number?  But they don't bother to have a --version
option?

Anyway, if this is an OpenBSD m4 compatibility issue, how about if you
start by installing GNU m4, and using that?  If that works, you're
done, except perhaps for sending a bug report to the OpenBSD m4 guys.
I know they want to be compatible with GNU m4, and would be happy to
hear of any bugs in that area.