Re: CSTD=c99 breaks package creation

From: David Schultz <das_at_FreeBSD.ORG>
Date: Fri, 13 Jun 2003 00:55:41 -0700
On Thu, Jun 12, 2003, Tim Robbins wrote:
> On Wed, Jun 11, 2003 at 07:37:01PM -0700, Kris Kennaway wrote:
> 
> > It's possible that there's either a bug in gcc or there is C code in
> > the system that has a different meaning when interpreted to C99
> > standards.
> 
> I think I may have found the problem, and I think it's in GNU tar.
> 
> GNU tar does this:
> 
> #ifndef __attribute__
> /* This feature is available in gcc versions 2.5 and later.  */
> # if __GNUC__ < 2 || (__GNUC__ == 2 && __GNUC_MINOR__ < 5) || __STRICT_ANSI__
> #  define __attribute__(Spec) /* empty */
> # endif
> #endif
> 
> machine/_types.h does this:
> 
> typedef int __attribute__((__mode__(__DI__)))           __int64_t;
> typedef unsigned int __attribute__((__mode__(__DI__)))  __uint64_t;
> 
> If __attribute__ is empty, __int64_t becomes a synonym for int. Bad.

Wow!  Nice catch...
Received on Thu Jun 12 2003 - 22:55:44 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:11 UTC