From: "Miquel van Smoorenburg" <miquels@cistron.nl>
Subject: Re: [RFC] Splitting kernel headers and deprecating __KERNEL__
Date: Wed, 1 Dec 2004 00:23:24 +0000 (UTC)
Organization: Cistron Group
Message-ID: <coj2ts$hhp$1@news.cistron.nl>
References: <Pine.LNX.4.58.0411281710490.22796@ppc970.osdl.org> <20041130224851.GH8040@waste.org> <20041130225128.GA31216@infradead.org> <41ACFDAF.3040209@nortelnetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Originator: miquels@cistron-office.nl (Miquel van Smoorenburg)
To: linux-kernel@vger.kernel.org
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 898
Lines: 19

In article <41ACFDAF.3040209@nortelnetworks.com>,
Chris Friesen  <cfriesen@nortelnetworks.com> wrote:
>Christoph Hellwig wrote:
>
>>>b) when include/user is deemed sufficiently populated, a flag day is
>>>declared and links from /usr/include are switched to them
>> 
>> 
>> there are no such links, only copies (more or less modified)
>
>This may be somewhat heretical, but someone has to ask...
>
>Once include/user/foo.h is sufficiently clean and sufficiently complete, is 
>there any reason to not allow such links?

It would be cleaner to use gcc -I /lib/modules/`uname -r`/build/include
so that you don't break regular compiles by accident.

Mike.

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