From: Segher Boessenkool <segher@kernel.crashing.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Andi Kleen <ak@suse.de>, linux arch <linux-arch@vger.kernel.org>,
Tony Luck <tony.luck@intel.com>,
kbuild devel <kbuild-devel@lists.sourceforge.net>
Subject: Re: kbuild: enable possibility to specify xFLAGS on commandline
Date: Sun, 9 Sep 2007 20:26:16 +0200 [thread overview]
Message-ID: <214e7ea7cfce67dca284414d82062854@kernel.crashing.org> (raw)
In-Reply-To: <20070909180254.GA20086@uranus.ravnborg.org>
> powerpc I dave a toolchain but defconfig seems not to be present.
powerpc uses
KBUILD_DEFCONFIG := $(shell uname -m)_defconfig
to automagically pick the defconfig you want, but that obviously
doesn't work for cross-builds.
pmac32_defconfig and pseries_defconfig are probably used the most,
you might want to test with one of those next time.
Segher
next prev parent reply other threads:[~2007-09-09 18:26 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 ` CPP includes ([PATCH 3/4] ia64: fix sn to add include files using EXTRA_CFLAGS) Oleg Verych
2007-09-11 13:48 ` [PATCH 3/4] ia64: fix sn to add include files using EXTRA_CFLAGS 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 ` Segher Boessenkool [this message]
2007-09-10 1:17 ` kbuild: enable possibility to specify xFLAGS on commandline 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=214e7ea7cfce67dca284414d82062854@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).