[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#434520: marked as done (__s64 / __u64 not defined in strict ansi mode)

Your message dated Tue, 27 May 2008 16:21:40 +0200
with message-id <20080527142140.GC3287@stro.at>
and subject line Re: __s64 / __u64 not defined in strict ansi mode
has caused the Debian Bug report #434520,
regarding __s64 / __u64 not defined in strict ansi mode
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
434520: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=434520
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-libc-dev
Version: 2.6.21-6
Severity: normal

i386 (and most likely all other arches too) don't define __s64 and
__u64 when -ansi is used: (extract from asm-xxx/types.h)

#if defined(__GNUC__) && !defined(__STRICT_ANSI__)
typedef __signed__ long long __s64;
typedef unsigned long long __u64;
#endif

This is needless (because gcc recognises that file as a system header
and doesn't complain about long long there) and makes it impossible to
use -ansi for apps / libs which include a kernel header that uses this
data type (for example linux/dvb/dmx.h).

The proposed solution is to remove the second part of the macro " &&
!defined(__STRICT_ANSI__)" in the headers.

Christoph

--- End Message ---
--- Begin Message --- 
Version: 2.6.25-1

commit 7437a51b30743ff1488981a393fc9e67894bf757
"Remove __STRICT_ANSI__ from linux/types.h" fixed the
described issue.

-- 
maks

--- End Message ---
Reply to: