From: Christoph Hellwig <hch@ns.caldera.de>
To: Keith Owens <kaos@ocs.com.au>
Cc: Christoph Hellwig <hch@ns.caldera.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] reiserfs patch for linux-2.4.2
Date: Thu, 1 Mar 2001 01:05:21 +0100 [thread overview]
Message-ID: <20010301010521.A7301@caldera.de> (raw)
In-Reply-To: <20010228202733.A18073@caldera.de> <20472.983404919@kao2.melbourne.sgi.com>
In-Reply-To: <20472.983404919@kao2.melbourne.sgi.com>; from kaos@ocs.com.au on Thu, Mar 01, 2001 at 11:01:59AM +1100
On Thu, Mar 01, 2001 at 11:01:59AM +1100, Keith Owens wrote:
> On Wed, 28 Feb 2001 20:27:33 +0100,
> Christoph Hellwig <hch@ns.caldera.de> wrote:
> >Urgg. limits.h is a userlevel header...
> >
> >The attached patch will make similar atempts fail (but not this one as
> >there is also a limits.h in gcc's include dir).
> >
> >--- linux-2.4.0/Makefile Mon Dec 25 19:21:14 2000
> >-CPPFLAGS := -D__KERNEL__ -I$(HPATH)
> >+GCCINCDIR = $(shell gcc -print-search-dirs | sed -ne 's/install: \(.*\)/\1include/gp')
> >+CPPFLAGS := -D__KERNEL__ -nostdinc -I$(HPATH) -I$(GCCINCDIR)
>
> cc: trimmed to l-k.
>
> CPPFLAGS apply to the kernel compiler which can be a cross compiler but
> you are extracting data from the host gcc. What exactly are you trying
> to do here?
Prevent inclusion of the usual (/usr/include) headers.
> Are you trying to prevent the use of user space includes
> or are you trying to pick up the cross compiler includes?
Ok, gcc should be replaced by $(CC).
Christoph
--
Of course it doesn't work. We've performed a software upgrade.
next prev parent reply other threads:[~2001-03-01 1:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-28 19:21 [PATCH] reiserfs patch for linux-2.4.2 Alexander Zarochentcev
2001-02-28 19:27 ` Christoph Hellwig
2001-03-01 0:01 ` Keith Owens
2001-03-01 0:05 ` Christoph Hellwig [this message]
2001-03-01 3:16 ` Albert D. Cahalan
2001-03-01 8:18 ` Christoph Hellwig
2001-03-02 0:35 ` Albert D. Cahalan
2001-03-01 0:39 ` Erik Mouw
2001-03-01 10:36 ` [reiserfs-dev] " Alexander Zarochentcev
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=20010301010521.A7301@caldera.de \
--to=hch@ns.caldera.de \
--cc=kaos@ocs.com.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.