From: William Pettersson <enigma@strudel-hound.com>
To: buildroot@busybox.net
Subject: [Buildroot] ARCH not being sent by make menuconfig - kernel compile fails to start
Date: Thu, 19 Jul 2007 10:52:11 +1000 [thread overview]
Message-ID: <469EB5BB.1090506@strudel-hound.com> (raw)
In-Reply-To: <469DE854.6090401@strudel-hound.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
William Pettersson wrote:
> First off, sorry for the cross-post. I posted this to the busybox
> mailing list first, instead of the buildroot list. My bad there, but
> since that was completely the wrong mailing list, I'm posting it here.
>
>
> So, I'm trying to set up a buildroot image for a soekris net4801. I ran
> make menuconfig, Target Architecture is set to "i386", Target
> Architecture Variant is set to "geode".
>
> However, when I run "make", I get the following
> (cd /home/wpettersson/src/buildroot/build_/linux-2.6.21.5 ; \
> /usr/bin/make -j1 ARCH= CC="/usr/bin/gcc" \
>
> INSTALL_HDR_PATH=/home/wpettersson/src/buildroot/toolchain_build_/linux
> headers_install ; \
> )
> make[1]: Entering directory
> `/home/wpettersson/src/buildroot/build_/linux-2.6.21.5'
> Makefile:491:
> /home/wpettersson/src/buildroot/build_/linux-2.6.21.5/arch//Makefile: No
> such file or directory
> make[1]: *** No rule to make target
> `/home/wpettersson/src/buildroot/build_/linux-2.6.21.5/arch//Makefile'.
> Stop.
> make[1]: Leaving directory
> `/home/wpettersson/src/buildroot/build_/linux-2.6.21.5'
> make: ***
> [/home/wpettersson/src/buildroot/toolchain_build_/linux/.configured] Error 2
>
> From the looks of it, "ARCH" isn't being set, which stuffs things up.
> I've tested by running the make command manually, with ARCH=i386, and
> that seemed to work.
>
> I wasn't sure which configuration files would be required, so to save
> space I didn't include any. If any are wanted, I'll gladly post them.
>
> Anyone know where ARCH is meant to be set?
Ok, I've investigated some more. If the Target Architecture Variant is
set to "i386", I get the following
wpettersson ~/buildroot/package/config/buildroot-config $ grep i386 *
auto.conf:BR2_i386=y
auto.conf:BR2_ARCH="i386"
auto.conf:BR2_x86_i386=y
auto.conf:BR2_GCC_TARGET_ARCH="i386"
auto.conf:BR2_GCC_TARGET_TUNE="i386"
autoconf.h:#define BR2_i386 1
autoconf.h:#define BR2_ARCH "i386"
autoconf.h:#define BR2_x86_i386 1
autoconf.h:#define BR2_GCC_TARGET_ARCH "i386"
autoconf.h:#define BR2_GCC_TARGET_TUNE "i386"
However, if I set Target Architecture Variant to "geode", I get
wpettersson ~/buildroot/package/config/buildroot-config $ grep geode *
auto.conf:BR2_x86_geode=y
auto.conf:BR2_GCC_TARGET_ARCH="geode"
auto.conf:BR2_GCC_TARGET_TUNE="geode"
autoconf.h:#define BR2_x86_geode 1
autoconf.h:#define BR2_GCC_TARGET_ARCH "geode"
autoconf.h:#define BR2_GCC_TARGET_TUNE "geode"
So selecting "geode" means that BR2_ARCH doesn't get set. I'm still
trying to dig through the code, but am I heading in the right direction
with this?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGnrW6NSpXjKoV00kRAgELAJ4hfXcvKXHc34mKkrIczzajeGtLGQCeLnjP
sRIaHdsUx5D3IQ6H/lciR7o=
=lkkM
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2007-07-19 0:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-18 10:15 [Buildroot] ARCH not being sent by make menuconfig - kernel compile fails to start William Pettersson
2007-07-19 0:52 ` William Pettersson [this message]
2007-07-19 3:55 ` William Pettersson
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=469EB5BB.1090506@strudel-hound.com \
--to=enigma@strudel-hound.com \
--cc=buildroot@busybox.net \
/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.