This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Build problem on AIX 5.1 in libiberty, uint64_t definition


On AIX 5.1, the GCC build fails as follows:
<< gcc -c -DHAVE_CONFIG_H -g -O2 -I. \
     -I/nile.g/bosch/gnu/gcc/libiberty/../include  -W -Wall -Wtraditional \
     -pedantic /nile.g/bosch/gnu/gcc/libiberty/make-temp-file.c
   In file included from /usr/include/sys/cred.h:36,
   from /usr/.../gcc-lib/powerpc-ibm-aix4.3.2.0/2.8.1/include/sys/file.h:24,
   from /.../gcc/libiberty/make-temp-file.c:36:
   /usr/include/sys/capabilities.h:26: parse error before `uint64_t'

This appears to be a result of the following in sys/types.h:

   typedef signed char             int8_t;
   typedef signed short            int16_t;
   typedef signed int              int32_t;
   #ifdef  __64BIT__
   typedef signed long             int64_t;
   #else   /* _ILP32 */
   #if defined(_LONG_LONG)
   typedef signed long long        int64_t;
   #endif
   #endif

   typedef unsigned char           uint8_t;
   typedef unsigned short          uint16_t;
   typedef unsigned int            uint32_t;
   #ifdef  __64BIT__
   typedef unsigned long           uint64_t;
   #else   /* _ILP32 */
   #if defined(_LONG_LONG)
   typedef unsigned long long      uint64_t;
   #endif
   #endif

In other words, a 32-bit compiler should define _LONG_LONG to indicate
support of this type. I'd like to fix this problem in the proper way,
but I don't know What would be the proper way of having configure do this?

Thanks in advance for any insight.

  -Geert


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]