On Sun, 26 Mar 2006, Kyle Moffett said:
> On Sun, 26 Mar 2006 06:52:05 -0500 Kyle Moffett <[email protected]> wrote:
>> 2) Since most of the headers are currently quite broken with respect to
>> GLIBC and userspace, I won't spend much extra time preserving
>> compatibility with GLIBC, userspace, or non-GCC compilers.
>
> That didn't come out right, but what I meant to say was this: Since the
> headers in include/linux are quite broken with respect to GLIBC and
> userspace, I won't let so-called "compatibility" code like this get in
> the way:
As long as the eventual goal is something that *works* with glibc and
uClibc and the rest of them, that's good enough as far as I can tell.
Obviously compatibility crud *in the headers* which serves no obvious
purpose and which userspace doesn't actually need should die (and
there's certainly some like that lying around).
--
`Come now, you should know that whenever you plan the duration of your
unplanned downtime, you should add in padding for random management
freakouts.'
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
