On Jan 29 2008 19:16, Mike Frysinger wrote:
quoted text
>> >> Some kernel headers exported to userspace rely on these 64bit
>> >> aligned defines. However, they are hidden behind
>> >> __KERNEL_STRICT_NAMES at the moment which means most of the time,
>> >> they're never actually available.
>>
>> Wrong way.
>
>i'm thinking the right way, i just may not have expressed it completely 
>clearly ...
>
>> They are inside #ifndef __KERNEL_STRICT_NAMES, so 
>> they _are_ available to userspace.
>
>for all practical purposes, they are not.  glibc will define 
>__KERNEL_STRICT_NAMES because (like a sane C lib), it defines all of the 
>basic types that the kernel also defines.

Phew - now we have two sorts of userspace? (Those with glibc and
those without, aka standalone). Right, it's messy, which is why
this thread exists and a better solution is sought :)
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/