From: Russell King <rmk@arm.linux.org.uk>
To: Erik Andersen <andersen@codepoet.org>,
Jeff Garzik <jgarzik@mandrakesoft.com>,
Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>,
Paul P Komkoff Jr <i@stingr.net>,
linux-kernel@vger.kernel.org
Subject: Re: 2.5.19 - What's up with the kernel build?
Date: Thu, 30 May 2002 10:01:44 +0100 [thread overview]
Message-ID: <20020530100144.B10611@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0205292019090.9971-100000@chaos.physics.uiowa.edu> <3CF5E698.2020806@mandrakesoft.com> <20020530085413.GA29170@codepoet.org>
On Thu, May 30, 2002 at 02:54:13AM -0600, Erik Andersen wrote:
> On Thu May 30, 2002 at 04:45:12AM -0400, Jeff Garzik wrote:
> > A small request to add to the list:
> >
> > Current 2.4.x kernels build (at least on x86) with
> > -nostdinc -I /usr/lib/gcc-lib/i586-mandrake-linux-gnu/3.0.4/include
>
> Shockingly, not everyone uses mandrake's gcc 3.0.4... ;-)
>
> GCCINCDIR:= ${shell $(CC) -print-search-dirs | sed -ne "s/install: \(.*\)/\1include/gp"}
> CFLAGS+=-nostdinc -I $(GCCINCDIR)
There is a nicer way of achieving the same thing:
CFLAGS += -nostdinc -iwithprefix include
`-iwithprefix DIR'
Add a directory to the second include path. The directory's name
is made by concatenating PREFIX and DIR, where PREFIX was
specified previously with `-iprefix'. If you have not specified a
prefix yet, the directory containing the installed passes of the
compiler is used as the default.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2002-05-30 9:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-29 20:22 2.5.19 - What's up with the kernel build? Kai Germaschewski
2002-05-29 20:50 ` Paul P Komkoff Jr
2002-05-29 20:58 ` Jeff Garzik
2002-05-29 22:38 ` Nicolas Pitre
2002-05-29 22:56 ` Thunder from the hill
2002-05-29 23:18 ` Nicolas Pitre
2002-05-29 23:29 ` Daniel Phillips
2002-05-29 23:06 ` Tomas Szepe
2002-05-29 23:40 ` Daniel Phillips
2002-05-30 0:17 ` Nicolas Pitre
2002-05-30 0:36 ` Daniel Phillips
2002-05-30 0:42 ` Jeff Garzik
2002-05-30 0:47 ` Robert Love
2002-06-03 6:49 ` Rusty Russell
2002-05-30 2:23 ` Nicolas Pitre
2002-05-30 2:30 ` Daniel Phillips
2002-05-30 2:00 ` Kai Germaschewski
2002-05-30 2:17 ` Daniel Phillips
2002-05-30 8:45 ` Jeff Garzik
2002-05-30 8:54 ` Erik Andersen
2002-05-30 9:01 ` Russell King [this message]
2002-05-30 9:32 ` Erik Andersen
2002-05-30 13:22 ` Kai Germaschewski
2002-05-29 22:14 ` Martin Dalecki
2002-05-29 23:22 ` Tom Rini
2002-05-29 22:45 ` Martin Dalecki
2002-05-30 0:33 ` Kai Germaschewski
2002-06-01 3:01 ` Kernel compile quiet mode Kevin O'Connor
2002-06-01 7:34 ` Kai Germaschewski
2002-06-01 15:08 ` Kevin O'Connor
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=20020530100144.B10611@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=andersen@codepoet.org \
--cc=i@stingr.net \
--cc=jgarzik@mandrakesoft.com \
--cc=kai@tp1.ruhr-uni-bochum.de \
--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