Re: kbuild feature/question: default ARCH
- From: Sam Ravnborg <sam@xxxxxxxxxxxx>
- Date: Wed, 14 Feb 2007 10:11:44 +0100
On Tue, Feb 13, 2007 at 10:06:19PM -0800, Randy Dunlap wrote:
Hi,Another approach I have been toying with previously was to
I'd like for kbuild to default ARCH to the already-symlinked
arch in include/asm-$(ARCH) if ARCH is not specified on the
command line or in the environment.
include ARCH in .config. But I somehow failed
to get it working and it went on my TODO list.
If kconfig get extended to so it can include Kconfig
files for all archs then it could be a Kconfig
option like anything else to select architecture
and this would also solve your issue.
As for the "export ARCH=i386" proposal this is of no
use for people crosscompiling a lot.
Think of the 'Al Viro' setup with crosscompile for 5+
different architectures.
But as I have no patches this is just cheap talk for now.
Sam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- [pp] kbuild: ARCH-setup (Re: kbuild feature/question: default ARCH)
- From: Oleg Verych
- [pp] kbuild: ARCH-setup (Re: kbuild feature/question: default ARCH)
- References:
- kbuild feature/question: default ARCH
- From: Randy Dunlap
- kbuild feature/question: default ARCH
- Prev by Date: SATA-performance part 2
- Next by Date: Re: [Xen-devel] Re: [patch 05/21] Xen-paravirt: paravirt_ops: allocate a fixmap slot
- Previous by thread: Re: kbuild feature/question: default ARCH
- Next by thread: [pp] kbuild: ARCH-setup (Re: kbuild feature/question: default ARCH)
- Index(es):
Relevant Pages
|
|