Re: bug in bison-1.875

[Paul Eggert]

Martin MOKREJŠ <address@hidden> writes:

>  I checked current cvs version on Tru65Unix 5.1A and now all tests succeed or
> get skipped. Is there any explanation what happened to the code that now I do
> not observer failures when bison get's compiled with -O2 CFLAG?

Sorry, I don't know.

>  However, although cc crashes on the _Bool testcase run by configure, 
> configure
> writes to stdout that _Bool is available. Shouldn' it say no?

Yes, it should say "no".

> checking for stdbool.h that conforms to C99... no
> checking for _Bool... yes

What is the corresponding log output?  I am looking for the output of
the following fragment in configure.  If the compiler crashed, then
the first "ac_status=$?" quoted below should set ac_status to a
nonzero value.  The next "echo" statement logs that value, so I'd
like to see what it is.


echo "$as_me:$LINENO: checking for stdbool.h that conforms to C99" >&5
echo $ECHO_N "checking for stdbool.h that conforms to C99... $ECHO_C" >&6
...
if { (eval echo "$as_me:$LINENO: \"$ac_compile\"") >&5
  (eval $ac_compile) 2>&5
  ac_status=$?
  echo "$as_me:$LINENO: \$? = $ac_status" >&5
  (exit $ac_status); } &&
         { ac_try='test -s conftest.$ac_objext'
  { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
  (eval $ac_try) 2>&5
  ac_status=$?
  echo "$as_me:$LINENO: \$? = $ac_status" >&5
  (exit $ac_status); }; }; then
  ac_cv_header_stdbool_h=yes
else
  echo "$as_me: failed program was:" >&5
sed 's/^/| /' conftest.$ac_ext >&5

ac_cv_header_stdbool_h=no
fi