All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Verych <olecom@flower.upol.cz>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux arch <linux-arch@vger.kernel.org>, Andi Kleen <ak@suse.de>,
	kbuild devel <kbuild-devel@lists.sourceforge.net>,
	Tony Luck <tony.luck@intel.com>
Subject: CPP includes ([PATCH 3/4] ia64: fix sn to add include files using EXTRA_CFLAGS)
Date: Mon, 10 Sep 2007 00:45:52 +0200	[thread overview]
Message-ID: <20070909224552.GF475@flower.upol.cz> (raw)
In-Reply-To: <20070909180623.GD20086@uranus.ravnborg.org>

On Sun, Sep 09, 2007 at 08:06:23PM +0200, Sam Ravnborg wrote:
> Changing the global CPPFLAGS is not the recommended way
> to add additional include dirs.
> Changed to use EXTRA_CFLAGS.

Maybe same magic can be applied to Rusty's "../../../" in i386
asm-offsets? Noone seems to use cpp's features much.

BTW, asm-values[0] are just don't needed any more?

[0] http://marc.info/?l=linux-kernel&s=asm-values
____

  reply	other threads:[~2007-09-09 22:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-09 18:02 kbuild: enable possibility to specify xFLAGS on commandline Sam Ravnborg
2007-09-09 18:04 ` [PATCH 1/4] kbuild: enable 'make CFLAGS=...' to add additional options to CC Sam Ravnborg
2007-09-09 18:05 ` [PATCH 2/4] kbuild: enable 'make AFLAGS=...' to add additional options to AS Sam Ravnborg
2007-09-09 18:06 ` [PATCH 3/4] ia64: fix sn to add include files using EXTRA_CFLAGS Sam Ravnborg
2007-09-09 22:45   ` Oleg Verych [this message]
2007-09-11 13:48   ` Jes Sorensen
2007-09-09 18:07 ` [PATCH 4/4] kbuild: enable 'make CPPFLAGS=...' to add additional options to CPP Sam Ravnborg
2007-09-09 18:26 ` kbuild: enable possibility to specify xFLAGS on commandline Segher Boessenkool
2007-09-10  1:17   ` Stephen Rothwell

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=20070909224552.GF475@flower.upol.cz \
    --to=olecom@flower.upol.cz \
    --cc=ak@suse.de \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=linux-arch@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=tony.luck@intel.com \
    /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.