Re: Bison 2.0 test suite on Mac OS X.3.8

[Paul Eggert]

Hans Aberg <address@hidden> writes:

>>What are CC, CFLAGS, and CPPFLAGS set to on your host?  That
>>might explain the problem.
>
> Do you mind to help me a bit on this.

Try doing this:

  cd tests
  ./testsuite -v -d 5
  grep -E '(CC|CFLAGS|CPPFLAGS|LDFLAGS|abs_top_builddir)=' testsuite.log

Assuming the output looks something like this:

  | abs_top_builddir='/some/long/path'
  | CC='gcc'
  | CFLAGS='-g -O2  '
  | CPPFLAGS="-DHAVE_CONFIG_H=1 -I$abs_top_builddir "
  | GCC='yes'
  | LDFLAGS=''

then execute these commands:

  abs_top_builddir='/some/long/path'
  CC='gcc'
  CFLAGS='-g -O2  '
  CPPFLAGS="-DHAVE_CONFIG_H=1 -I$abs_top_builddir "
  LDFLAGS=''
  cd testsuite.dir/005
  set -x
  $CC $CFLAGS $CPPFLAGS -c input.c -o input.o
  $CC $CFLAGS $CPPFLAGS -c main.c -o main.o
  $CC $CFLAGS $CPPFLAGS $LDFLAGS input.o main.o $LIBS -o input

Please email to bison-bugs the output of all the above commands
(including the "grep").


> It is a bit strange that maiking bison works, without those flags
> then, but the test suite fails. How is it setup in the "make" of
> Bison, as these falgs then are not needed?

"make check" can exercise features of the underlying system that
"make" and "make install" do not.