Re: [Cvs-dev] Re: [Cvs-test-results] Build CVS (TRUNK) failed.

[Larry Jones]

Mark D. Baushke writes:
> 
> It would also be a great idea if the information about the breakage for
> the SGI builds could be forwarded to hte cvs-test-results list.

Well, it appears that it is compiling now, but only by accident. 
The problem, which Derek and I discussed a while ago but never resolved,
is that SGI provides a <stdint.h> that only works in C99 mode, but
configure doesn't detect that because the SGI compiler doesn't consider
a #error directive as fatal, it just issues a warning and continues,
leading to lots of compile warnings like:

source='/u/scjones/cvs-nightly/src/add.c' object='add.o' libtool=no \
DEPDIR=.deps depmode=sgi /bin/sh /u/scjones/cvs-nightly/build-aux/depcomp \
cc -mips3 -DHAVE_CONFIG_H -I. -I/u/scjones/cvs-nightly/src -I..  
-I/u/scjones/cvs-nightly/lib -I../lib -I/u/scjones/cvs-nightly/diff 
-I/u/scjones/cvs-nightly/zlib -Ino/include  -g -c 
/u/scjones/cvs-nightly/src/add.c
cc-1035 cc: WARNING File = /usr/include/stdint.h, Line = 5
  #error directive:  This header file is to be used only for c99 mode
          compilations

  #error This header file is to be used only for c99 mode compilations
   ^

Since <inttypes.h> has been around a lot longer than <stdint.h> and is
supposed to define all the same stuff (plus more), I think the right
thing to do is include just <inttypes.h> if it exists, and only include
<stdint.h> if it doesn't.  The only problem is that many of the files
that include <stdint.h> are in the lib directory and come from gnulib
rather than being our source files.

-Larry Jones

It's no fun to play games with a poor sport. -- Calvin