This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: CVS-19981209: Patch for "unsigned HOST_WIDE_INT" on Solaris2.6
- To: Paul Eggert <eggert at twinsun dot com>
- Subject: Re: CVS-19981209: Patch for "unsigned HOST_WIDE_INT" on Solaris2.6
- From: Jim Wilson <wilson at cygnus dot com>
- Date: Mon, 14 Dec 1998 13:39:58 -0800
- cc: law at cygnus dot com, moshier at mediaone dot net, manfred at s-direktnet dot de, Manfred dot Hollstein at ks dot sel dot alcatel dot de, brolley at cygnus dot com, egcs-patches at cygnus dot com, gcc2 at gnu dot org
It is only an irix5 problem, it is not an irix6 problem. Under irix5, there
is an inttypes.h file, but it isn't useful, because it clashes with
<sys/types.h>. This should not prevent use of inttypes.h on any machine
with a useful inttypes.h file.
henway<6>cat tmp.c
#include <sys/types.h>
#include <inttypes.h>
henway<7>cc tmp.c
cfe: Error: /usr/include/inttypes.h, line 61: redeclaration of 'int8_t'; previous declaration at line 211 in file '/usr/include/sys/types.h'
typedef signed char int8_t;
------- ----------- ^
...
To make matters more confusing, gcc gives a warning instead of an error for
this case, because the two type definitions are identical. Thus whether
inttypes.h is usable depends on which compiler you use. If you configure
using gcc, and then try to build using cc, the build could fail with the above
error. You aren't supposed to use a different compiler for configuring and
building anyways, but we unconditionally disable use of inttypes.h for an
irix5 host just to be sure.
Jim