Le 20 mars 2012 à 12:38, gccbison a écrit :
> On 2012-03-20 09:07, Akim Demaille wrote:
>> I don't understand this: these tests run the C compiler, not
>> the C++ one. Besides, configure.ac is already pay attention
>> not to pass C flags to g++.
>
> It looks to be a GCC issue and does only happen when using
> the '--enable-gcc-warnings' option at ./configure as this:
>
> /configure CC="/home/myself/bin/mygcc/bin/gcc"
> --prefix=$HOME/bin/mybison2.5gee --exec-prefix=$HOME/bin/mybison2.5gee
> --program-prefix=my --enable-gcc-warnings
>
> gcc (GCC) 4.8.0 20120319 (experimental)
> Copyright (C) 2012 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Well, the problem is here:
testsuite: command line was:
$ ./tests/testsuite -C tests CC=g++
You run the test suite with CC = a C++ compiler. This is something
you should report as soon as possible.
Is this because of some Make target? We have this:
# Be real mean with it.
.PHONY: maintainer-check-g++
maintainer-check-g++: $(TESTSUITE)
$(RUN_TESTSUITE) CC='$(CXX)'
which shows we should be more careful about the flags in that case.
Yet, I wonder why there would be so few failures. Maybe all the
other tests have the same warnings, but the real problem is that of
the synclines. I see, btw, that:
Skipped tests:
GNU Bison 2.5.795-7098 test suite test groups:
NUM: FILE-NAME:LINE TEST-GROUP-NAME
KEYWORDS
119: synclines.at:110 Prologue synch line
120: synclines.at:127 %union synch line
121: synclines.at:147 Postprologue synch line
122: synclines.at:170 Action synch line
123: synclines.at:189 Epilogue synch line
Could you please send one of the corresponding logs? Say
testsuite.dir/119/test-suite.log.
I checked the #line in the generated c file, and, for a human,
they look alright, I don't see what is troubling g++. Do you
have the same issues with the C compiler?
