From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Machine Configuration
Date: Thu, 20 Oct 2011 23:44:21 +0200 [thread overview]
Message-ID: <j7q4nl$akr$1@dough.gmane.org> (raw)
In-Reply-To: <4EA073C0.7000502@mlbassoc.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 20-10-11 21:17, Gary Thomas schreef:
> On 2011-10-20 11:45, Russell Morris wrote:
>> Hi,
>>
>> I am trying to do some builds for an am3517-evm ... but the machine
>> configuration doesn't seem to be working (or I'm doing it wrong, more
>> likely ... :-().
>>
>> I have successfully built console-image for qemuarm, and then use
>> oebb.sh to set the machine (to am3517-evm, followed bu ./oebb.sh
>> update) - but then when I try to build for this machine I see the
>> following ...
>>
>> OE Build Configuration: BB_VERSION = "1.13.3" TARGET_ARCH
>> = "arm" TARGET_OS = "linux-gnueabi" MACHINE =
>> "qemuarm" DISTRO = "angstrom" DISTRO_VERSION =
>> "v2011.10-core" TUNE_FEATURES = "armv5 dsp thumb arm926ejs"
>> TARGET_FPU = "soft"
>>
>> So it's still building for qemuarm, not am3517-evm ... :-(. Is anyone
>> else having this issue? Any suggestions of how to fix this?
>
> You need to always specify MACHINE="am3517-evm" on your command line,
> e.g. % MACHINE="am3517-evm" bitbake systemd-image
>
> Alternatively, you can add just a single line to conf/local.conf and then
> it will be "sticky"
not local.conf, auto.conf
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org
iD8DBQFOoJY1MkyGM64RGpERAliKAKCfu0E2K3Qn+lsTx5YzNRgkxrA+QwCgqJjT
0ZsSMZCZArrGVc54VNa4dDA=
=zm3i
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-10-20 21:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-20 17:45 Machine Configuration Russell Morris
2011-10-20 19:17 ` Gary Thomas
2011-10-20 21:44 ` Koen Kooi [this message]
2011-10-20 22:17 ` Russell Morris
[not found] ` <CAMKF1soL9oEShqjfAfpyfEvq1XrHDNqE_-1R6PCdnsqUCPHmLg@mail.gmail.com>
2011-10-21 3:27 ` Russell Morris
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='j7q4nl$akr$1@dough.gmane.org' \
--to=koen@dominion.thruhere.net \
--cc=openembedded-devel@lists.openembedded.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