Skip to contentSkip to conversation

definition and usage of __u64/__s64 inconsistent?

2.6.0-test6 Michal Kochanowicz 2 participants 3 messages Oct 3, 2003

lore
Share & tools
lore
#0 lore raw

Hi!

The two types are _conditionally_ defined as follows (in asm/types.h):
#if defined(__GNUC__) && !defined(__STRICT_ANSI__)
typedef __signed__ long long __s64;
typedef unsigned long long __u64;
#endif

The file asm/types.h is _unconditionally_ included from linux/cdrom.h and linux/loop.h and both files use __u64 unonditionally. Isn't this an error?

Regards

PS. I came across this problem while trying to compile kdemultimedia-3.1.4 which uses linux/linux.h - if it does matter.

Signature · 4 lines
--= Michal Kochanowicz =--==--==BOFH==--==--= [email protected] =--
--= finger me for PGP public key or visit http://michal.waw.pl/PGP =--
--==--==--==--==--==-- Vodka. Connecting people.--==--==--==--==--==--
A chodzenie po górach SSIE!!!
#1 lore raw
Quoted 3 lines · On Fri, 3 Oct 2003 10:54:12 +0200 Michal Kochanowicz <[email protected]>…

The file asm/types.h is _unconditionally_ included from linux/cdrom.h and linux/loop.h and both files use __u64 unonditionally. Isn't this an error?

Not really.

We could fix this by using the __extension__ keyword and thereby get rid of the __STRICT_ANSI__ check and situations like your's would work.

#2 lore raw
Quoted 5 lines · David S. Miller

Not really.

We could fix this by using the __extension__ keyword and thereby get rid of the __STRICT_ANSI__ check and situations like your's would work.

OK, then question is: will you fix it? Or maybe it's application which should be fixed (how?) ?

Signature · 4 lines
--= Michal Kochanowicz =--==--==BOFH==--==--= [email protected] =--
--= finger me for PGP public key or visit http://michal.waw.pl/PGP =--
--==--==--==--==--==-- Vodka. Connecting people.--==--==--==--==--==--
A chodzenie po górach SSIE!!!