Re: Finally: 4.0 tagged, tarred and ready to test.

[Ethan M. <merritt@u.washington.edu>]

On Wednesday 14 April 2004 05:55 am, Hans-Bernhard Broeker wrote:
> On Tue, 13 Apr 2004, Ethan Merritt wrote:
> > Building on Tru64 using DEC cc generates a large number of
> > compiler warnings due to the re-definition of TBOOLEAN.
>
> Not of TBOOLEAN itself, I trust it, but of the system datatype __Bool or
> similar.  What were the results of configure tests on __Bool and
> <stdbool.h>?


configure:6215: checking for stdbool.h that conforms to C99
configure:6269: cc -c -g -I/usr/local/include  conftest.c >&5
cc: Severe: configure, line 6270: Cannot find file <stdbool.h> specified in #include directive.
#include <stdbool.h>

configure:6291: checking for _Bool
configure:6316: cc -c -g -I/usr/local/include  conftest.c >&5
cc: Error: configure, line 6382: Invalid expression.
if ((_Bool *) 0)
------------^

ac_cv_header_stdbool_h=no
ac_cv_type__Bool=no

> Was DEC cc successfully turned into ANSI-accepting (but 
> *not* strictly-ANSI-only) mode?

I believe that you can toggle acceptance/non-acceptance of
all the language features separately, but I just content myself
with using "cc -std1"  which is described as
"strict ISO C and ANSI C conformance"

-- 
Ethan A Merritt       merritt@u.washington.edu
Biomolecular Structure Center
Mailstop 357742
University of Washington, Seattle, WA 98195