Re: [GNU Bison 3.1] testsuite: 222 failed

[Yijun . Yu]

Did what you suggested, running

make check-local TESTSUITEFLAGS='-x 222'

at the root folder of the bison-3.1, the report was successful this time !

bison-3.1$ make check-local TESTSUITEFLAGS='-x 222'
/Library/Developer/CommandLineTools/usr/bin/make  all-recursive
Making all in po
make[2]: Nothing to be done for `all'.
Making all in runtime-po
make[2]: Nothing to be done for `all'.
Making all in .
  GEN      doc/bison.help
./tests/testsuite -C tests -x 222
## ------------------------- ##
## GNU Bison 3.1 test suite. ##
## ------------------------- ##
222: Several parsers                                 ok

## ------------- ##
## Test results. ##
## ------------- ##

1 test was successful.

I wonder why an error was reported when running ./testsuite inside the tests 
folder.
So I ran the full testsuite again. To my surprise, it is OK now. This is a bit 
strange,
but we can ignore the warning for now.


## ------------- ##
## Test results. ##
## ------------- ##

All 515 tests were successful.

Best regards,
Yijun



On 26 Sep 2018, at 17:01, Akim Demaille <address@hidden<mailto:address@hidden>> 
wrote:



Le 24 sept. 2018 à 22:32, Yijun.Yu <address@hidden<mailto:address@hidden>> a 
écrit :

I have tested it on Mac OSX 10.14.

222. headers.at:191<http://headers.at:191>: testing Several parsers ...
./headers.at:284<http://headers.at:284>: bison -fno-caret -d -o x1.c x1.y
./headers.at:284<http://headers.at:284>: $BISON_C_WORKS
stderr:
stdout:
./headers.at:284<http://headers.at:284>: $CC $CFLAGS $CPPFLAGS  -c -o x1.o x1.c
stderr:
stdout:
./headers.at:284<http://headers.at:284>: echo "x1" >>expout
./headers.at:285<http://headers.at:285>: bison -fno-caret -d -o x2.c x2.y
./headers.at:285<http://headers.at:285>: $BISON_C_WORKS
stderr:
stdout:
./headers.at:285<http://headers.at:285>: $CC $CFLAGS $CPPFLAGS  -c -o x2.o x2.c
stderr:
stdout:
./headers.at:285<http://headers.at:285>: echo "x2" >>expout
./headers.at:286<http://headers.at:286>: bison -fno-caret -d -o x3.c x3.y
./headers.at:286<http://headers.at:286>: $BISON_C_WORKS
stderr:
stdout:
./headers.at:286<http://headers.at:286>: $CC $CFLAGS $CPPFLAGS  -c -o x3.o x3.c
stderr:
stdout:
./headers.at:286<http://headers.at:286>: echo "x3" >>expout
./headers.at:287<http://headers.at:287>: bison -fno-caret -d -o x4.c x4.y
./headers.at:287<http://headers.at:287>: $BISON_C_WORKS
stderr:
stdout:
./headers.at:287<http://headers.at:287>: $CC $CFLAGS $CPPFLAGS  -c -o x4.o x4.c
stderr:
stdout:
./headers.at:287<http://headers.at:287>: echo "x4" >>expout
./headers.at:288<http://headers.at:288>: bison -fno-caret -d -o 
x5.cc<http://x5.cc> x5.y
./headers.at:288<http://headers.at:288>: $BISON_CXX_WORKS
stderr:
stdout:
./headers.at:288<http://headers.at:288>: $CXX $CXXFLAGS $CPPFLAGS  -c -o x5.o 
x5.cc<http://x5.cc>
stderr:
stdout:
./headers.at:288<http://headers.at:288>: echo "x5" >>expout
./headers.at:289<http://headers.at:289>: bison -fno-caret -d -o x6.c x6.y
./headers.at:289<http://headers.at:289>: $BISON_C_WORKS
stderr:
stdout:
./headers.at:289<http://headers.at:289>: $CC $CFLAGS $CPPFLAGS  -c -o x6.o x6.c
stderr:
stdout:
./headers.at:289<http://headers.at:289>: echo "x6" >>expout
./headers.at:290<http://headers.at:290>: bison -fno-caret -d -o x7.c x7.y
./headers.at:290<http://headers.at:290>: $BISON_C_WORKS
stderr:
stdout:
./headers.at:290<http://headers.at:290>: $CC $CFLAGS $CPPFLAGS  -c -o x7.o x7.c
stderr:
stdout:
./headers.at:290<http://headers.at:290>: echo "x7" >>expout
./headers.at:291<http://headers.at:291>: bison -fno-caret -d -o x8.c x8.y
./headers.at:291<http://headers.at:291>: $BISON_C_WORKS
stderr:
stdout:
./headers.at:291<http://headers.at:291>: $CC $CFLAGS $CPPFLAGS  -c -o x8.o x8.c
stderr:
stdout:
./headers.at:291<http://headers.at:291>: echo "x8" >>expout
./headers.at:327<http://headers.at:327>: $PERL -n -0777 -e '
 s{/\*.*?\*/}{}gs;
 s{//.*}{}g;
 s{\b(YYChar
     |YYPUSH_MORE(?:_DEFINED)?
     |YYUSE
     |YY_ATTRIBUTE(?:_PURE|_UNUSED)?
     |YY_IGNORE_MAYBE_UNINITIALIZED_(?:BEGIN|END)
     |YY_INITIAL_VALUE
     |YY_\w+_INCLUDED
     |YY_NULLPTR
     |(defined|if)\ YYDEBUG
     )\b}{}gx;
 while (/^(.*YY.*)$/gm)
 {
   print "$ARGV: invalid exported YY: $1\n";
 }
 if ($ARGV =~ /\.h$/)
 {
   while (/^(.*yy.*)$/gm)
   {
     print "$ARGV: invalid exported yy: $1\n";
   }
 }
' -- *.hh *.h
./headers.at:330<http://headers.at:330>: $BISON_C_WORKS
stderr:
stdout:
./headers.at:330<http://headers.at:330>: $CC $CFLAGS $CPPFLAGS  -c -o c-only.o 
c-only.c
stderr:
stdout:
./headers.at:330<http://headers.at:330>: $BISON_CXX_WORKS
stderr:
stdout:
./headers.at:330<http://headers.at:330>: $CXX $CXXFLAGS $CPPFLAGS  -c -o 
cxx-only.o cxx-only.cc<http://cxx-only.cc>
stderr:
stdout:
./headers.at:330<http://headers.at:330>: $CXX $CXXFLAGS $CPPFLAGS $LDFLAGS 
c-only.o cxx-only.o -o c-and-cxx ||
         exit 77
--- /dev/null 2018-09-19 21:51:47.000000000 +0100
+++ /Users/yy66/bison-3.1/tests/testsuite.dir/at-groups/222/stderr 2018-09-19 
21:51:50.000000000 +0100
@@ -0,0 +1,2 @@
+ld: warning: URGENT: building for OSX, but linking against dylib 
(/usr/lib/libc++.dylib) built for (unknown). Note: This will be an error in the 
future.
+ld: warning: URGENT: building for OSX, but linking against dylib 
(/usr/lib/libSystem.dylib) built for (unknown). Note: This will be an error in 
the future.
stdout:
222. headers.at:191<http://headers.at:191>: 222. Several parsers 
(headers.at:191<http://headers.at:191>): FAILED 
(headers.at:330<http://headers.at:330>)

well, it’s only a warning, we could just ignore it, that’s
easy to do.  But I’m a bit more worried on the fact that it
seems to mean that at some point it will cease to work.

But what exactly will cease to work?

Please, run the testsuite with

$ make check-local TESTSUITEFLAGS=‘-x 222’

and check send 222/testsuite.log.  It will show what exactly
was run by

$CXX $CXXFLAGS $CPPFLAGS $LDFLAGS c-only.o cxx-only.o -o c-and-cxx

so we might learn what is the problem here, and see if there’s
something cleaner to do.  Please, go into this directory, and
play with this command to see if you can get it run without this
warning.

Thanks!