golang / go

The Go programming language
https://go.dev
BSD 3-Clause "New" or "Revised" License
123.52k stars 17.6k forks source link

3 unexpected bugs "error message does not match 'syntax|signature'" #127

Closed gopherbot closed 9 years ago

gopherbot commented 14 years ago

by bortzmeyer:

What steps will reproduce the problem?
1. ./all.sh
2.
3.

What is the expected output? What do you see instead?

--- cd ../test
136,146d135
< =========== fixedbugs/bug121.go
< BUG: errchk: fixedbugs/bug121.go:12: error message does not match
'syntax|signature'
< errchk: fixedbugs/bug121.go:16: error message does not match
'syntax|signature'
< 
< =========== fixedbugs/bug125.go
< BUG: errchk: fixedbugs/bug125.go:11: error message does not match
'missing|syntax'
< errchk: fixedbugs/bug125.go: unmatched error messages:
< ==================================================
< fixedbugs/bug125.go:10: imported and not used: os
< ==================================================
< 
154,161d142
< =========== fixedbugs/bug166.go
< BUG: errchk: fixedbugs/bug166.go:11: missing expected error: 'syntax
error|expected ';''
< errchk: fixedbugs/bug166.go: unmatched error messages:
< ==================================================
< fixedbugs/bug166.go:10: parse error
< fixedbugs/bug166.go:10: e declared and not used
< ==================================================
< 
0 known bugs; 3 unexpected bugs; test output differs

What is your $GOOS?  $GOARCH?

GOROOT=/home/stephane/tmp/go
GOARCH=386
GOOS=linux

Which revision are you sync'ed to?  (hg log -l 1)

changeset:   4015:cb140bac9ab0
tag:         tip
user:        Russ Cox <rsc@golang.org>
date:        Thu Nov 12 14:55:26 2009 -0800
summary:     test/run: unset GREP_OPTIONS

Please provide any additional information below.

% uname -a
Linux horcrux 2.6.27-15-generic #1 SMP Tue Oct 20 06:52:09 UTC 2009 i686
GNU/Linux

% gcc --version
gcc (Ubuntu 4.3.2-1ubuntu12) 4.3.2

% lsb-info
Ubuntu 8.10 (intrepid)
rsc commented 14 years ago

Comment 1:

Could you please send the output of bison --version?
It looks like the parser is behaving differently than it
usually does.
Thanks.

Owner changed to r...@golang.org.

Status changed to WaitingForReply.

gopherbot commented 14 years ago

Comment 2 by bortzmeyer:

% bison --version
bison++ Version 1.21.9-1, adapted from GNU bison by coetmeur@icdc.fr
Maintained by Magnus Ekdahl <magnus@debian.org>
rsc commented 14 years ago

Comment 3:

The Go build requires bison, not bison++.
Did you install bison++ (as opposed to bison) intentionally?
If not, you could try removing bison++ and installing 
ordinary bison.  Or you could ignore the fact that these
tests are failing and use Go anyway, hoping that only
the syntax error cases differ between bison++ and bison.
If you run a build using plain bison, this will work fine.
Thanks for the report.

Status changed to WontFix.

gopherbot commented 14 years ago

Comment 4 by bortzmeyer:

OK, I was not even aware of the difference between bison and bison++. For me, the
later was simply a more recent version. I 'aptitude installed bison' and now
everything works:
% ./8.out 
hello, world
One more item for the FAQ :-)