From: Keith Owens <kaos@ocs.com.au>
To: Jeff Garzik <garzik@havoc.gtf.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Why 'linux/fs.h' cannot be included? I *can*...
Date: Thu, 31 Jan 2002 13:06:32 +1100 [thread overview]
Message-ID: <7661.1012442792@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Wed, 30 Jan 2002 20:57:14 CDT." <20020130205714.B20698@havoc.gtf.org>
On Wed, 30 Jan 2002 20:57:14 -0500,
Jeff Garzik <garzik@havoc.gtf.org> wrote:
>On Thu, Jan 31, 2002 at 12:51:50PM +1100, Keith Owens wrote:
>> tend not to live very long. Christoph Hellwig suggested a Makefile
>> change that prevents kernel code including user space headers, it is
>> included in kbuild 2.5 and there is a 2.4 version in
>>
>> http://marc.theaimsgroup.com/?l=linux-kernel&m=100321690511549&w=2
>
>Patch looks ok to me... The only thing I wonder is if we should put
>kernel includes before gcc includes, just in case we want to override
>something.
I doubt that is ever a good idea. The kernel would have to track which
gcc was being used and work out what to override or duplicate. Why
make the kernel any more sensitive to gcc than we have to?
>I would support putting this in the default cflags for 2.4 and 2.5...
--nostdinc is the default for kbuild 2.5. I did not bother sending it
in for 2.4 because my kbuild 2.5 testing finds the naughty code anyway
and I send individual bug fixes for the offending files. There is also
a risk of breaking existing third party code, I was not willing to take
that risk on a "stable" series like 2.4.
next prev parent reply other threads:[~2002-01-31 2:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1012391761.28301.linux-kernel2news@redhat.com>
2002-01-30 18:24 ` Why 'linux/fs.h' cannot be included? I *can* Pete Zaitcev
2002-01-30 23:33 ` Keith Owens
2002-01-31 1:17 ` Jeff Garzik
2002-01-31 1:51 ` Keith Owens
2002-01-31 1:57 ` Jeff Garzik
2002-01-31 2:06 ` Keith Owens [this message]
2002-01-31 2:35 ` Jeff Garzik
2002-01-30 12:07 DervishD
2002-01-30 14:27 ` Eric W. Biederman
2002-01-30 16:12 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2002-01-29 10:20 DervishD
2002-01-29 14:30 ` Jeff Garzik
2002-01-29 14:51 ` Alan Cox
2002-01-29 14:42 ` Jeff Garzik
2002-01-28 19:31 DervishD
2002-01-28 19:44 ` Eric W. Biederman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7661.1012442792@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=garzik@havoc.gtf.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox