From: David Miller <davem@davemloft.net>
To: bunk@kernel.org
Cc: cate@cateee.net, mingo@elte.hu, sam@ravnborg.org,
thomas@archlinux.org, tglx@linutronix.de,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
akpm@linux-foundation.org
Subject: Re: 2.6.24-rc1-82798a1 compile failure (x86_64)
Date: Sun, 04 Nov 2007 20:03:13 -0800 (PST) [thread overview]
Message-ID: <20071104.200313.236511775.davem@davemloft.net> (raw)
In-Reply-To: <20071104163439.GM12045@stusta.de>
From: Adrian Bunk <bunk@kernel.org>
Date: Sun, 4 Nov 2007 17:34:39 +0100
> But the main point that stuff like e.g. -I/usr/local/dist/include that
> might in some environments be correct for all and required for most
> userspace software should not leak into the kernel still stands.
You can have a "myconfigure" shell script that runs ./configure
in the current directory with the args you want for stuff like
that.
There is no need to contaminate your environment by setting
CFLAGS globally.
next prev parent reply other threads:[~2007-11-05 4:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 21:46 2.6.24-rc1-82798a1 compile failure (x86_64) Thomas Bächler
2007-10-29 22:12 ` Thomas Gleixner
[not found] ` <47266BF6.6070206@archlinux.org>
[not found] ` <alpine.LFD.0.9999.0710300033470.3186@localhost.localdomain>
2007-10-30 9:10 ` Thomas Bächler
2007-11-03 10:04 ` Thomas Bächler
2007-11-03 12:11 ` Sam Ravnborg
2007-11-04 2:02 ` Adrian Bunk
2007-11-04 10:04 ` Ingo Molnar
2007-11-04 10:19 ` Sam Ravnborg
2007-11-04 10:31 ` David Miller
2007-11-04 11:16 ` Sam Ravnborg
2007-11-04 12:27 ` Thomas Bächler
2007-11-04 15:29 ` Adrian Bunk
2007-11-04 15:55 ` Oleg Verych
2007-11-04 16:19 ` Giacomo Catenazzi
2007-11-04 16:34 ` Adrian Bunk
2007-11-04 18:33 ` Giacomo Catenazzi
2007-11-05 4:03 ` David Miller [this message]
2007-11-04 18:10 ` Sam Ravnborg
2007-11-05 4:01 ` David Miller
2007-11-06 17:32 ` Arjan van de Ven
2007-11-07 0:12 ` Adrian Bunk
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=20071104.200313.236511775.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=cate@cateee.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
--cc=thomas@archlinux.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