Thus saith Russ Allbery:
>
> Charles E Campbell <[EMAIL PROTECTED]> writes:
>
> > Vim doesn't appear to include <inttypes.h> anywhere and, after checking
> > out the files under /usr/include/..., none of them include <inttypes.h>
> > either. This is the first time I've had a problem with <sys/types.h>
> > conflicting with <inttypes.h>; looks like <inttypes.h> hasn't been
> > needed by any of the source I've ever compiled heretofore.
>
> In IRIX 6.5, the relevant section of <sys/types.h> looks like:
> #ifndef __inttypes_INCLUDED
> #define __inttypes_INCLUDED
No, this protection did not appear (until I just rudely put them in
manually :) . Since the likelihood that I'll be getting either a
hardware or software upgrade to my SGI is an excellent approximation
to zero, and if the machine dies its supposed to be excessed, this
manual fix shouldn't be a problem.
One interesting thing: the unsigned typedefs appear
in <inttypes.h> as uint8_t, uint16_t, and uint64_t,
but in <sys/types.h> as u_int8_t, u_int16_t, and u_int32_t.
So, after this mutilation a small test file with
#include <inttypes.h>
#include <sys/types.h>
(or in opposite order) now compiles. Back to Vim, the resulting
<config.h> file now appears to be generated properly. IMHO, looks
like perhaps there should be a check to see if <sys/types.h> and
<inttypes.h> can be simultaneously included.
Thank you,
Chip Campbell
--
Charles E Campbell, Jr, PhD _ __ __
Goddard Space Flight Center / /_/\_\_/ /
[EMAIL PROTECTED] /_/ \/_//_/
PGP public key: http://www.erols.com/astronaut/pgp.html