On Thu, 2003-11-06 at 20:32, Martin Schlemmer wrote: > On Thu, 2003-11-06 at 19:37, David S. Miller wrote: > > On Thu, 06 Nov 2003 19:36:39 +0200 > > Martin Schlemmer wrote: > > > > > On Tue, 2003-05-06 at 04:19, David S. Miller wrote: > > > > On Tue, 2003-05-06 at 02:16, Thomas Horsten wrote: > > > > > The following patch fixes the problem: > > > > > > > > Making the u64 swabbing functions unavailable is not an > > > > acceptable solution. > > > > > > > > > > Sorry to dig this up again, but wont __STRICT_ANSI__ assume > > > that the program will not use u64 functions (as the program/compiler > > > is supposed to adhere to ansi standards)? > > > > It may make indirect use of inline functions in the kernel headers > > in question, which themselves need to use the u64 type. > > Right, thanks. Actually, so what ? If we use -ansi, it means we in theory only use u16 and u32 as data types, and if the library that was compiled with u64 support wish to convert the u32 array/buffer pointer we pass to it to u64, it should make sure it setup things correctly. Ok, so maybe above is not a case to work on, but if I write an app that use only 32bit data types, and it links to a library that also handles 64bit, it does not matter, as I do not call the functions that handle 64bit data types, no ? Thanks, -- Martin Schlemmer