Message-ID: <3ED93CC6.30200@cox.net>
Date: Sat, 31 May 2003 16:37:42 -0700
From: "Kevin P. Fleming" <kpfleming@cox.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a) Gecko/20030401
MIME-Version: 1.0
To: "ismail (cartman) donmez" <kde@myrealbox.com>,
       LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] include/linux/sysctl.h needs linux/compiler.h
References: <3ED8D5E4.6030107@cox.net> <200305312358.03208.kde@myrealbox.com> <3ED919DC.6030202@cox.net> <200306010016.05548.kde@myrealbox.com>
In-Reply-To: <200306010016.05548.kde@myrealbox.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org

ismail (cartman) donmez wrote:
> On Sunday 01 June 2003 00:08, Kevin P. Fleming wrote:
> 
> 
>>Right. But until such time as that happens (even if started today that's
>>many months away), real world libraries need to be compiled to be used
>>against the new kernel.
>>
> 
> Yes I reported to binutils hackers that this change broke binutils ( + glibc ) 
> but kernel guys just say "do not include kernel headers in userspace" . 
> 

Oh, I saw that discussion. I fully agree. If I can help the process of 
creating a sanitized userspace set of kernel headers I'll be happy to.

In the meantime, a small change to a kernel header, that provides _zero_ 
functional difference to the kernel itself (it's only there for source 
code checkers, as best I can tell) shouldn't break existing userspace 
libraries.

If it's going to, then we should just go ahead and break everything and 
get it done right. It's late in the 2.6 game, but the first few steps on 
the path have already been taken.

-
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/