From: Radu Moisan <radu.moisan@intel.com>
To: Wolfgang Denk <wd@denx.de>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH][RFC] u-boot: Upgrade to upstream stable 2012.07
Date: Mon, 06 Aug 2012 17:09:23 +0300 [thread overview]
Message-ID: <501FD013.5040000@intel.com> (raw)
In-Reply-To: <20120806134641.E98B3203FD8@gemini.denx.de>
[-- Attachment #1: Type: text/plain, Size: 1000 bytes --]
CROSS_COMPILE is set in EXTRA_OEMAKE which is used in oe-runmake()
within do_compile()
Running devshell is achieved in do_devshell() which is run after
do_patch() but before do_compile(), that's why in devshell CROSS_COMPILE
is not (yet) set.
I think this is the intended way for things to work, devshell usage, as
I see it, is mainly for pre-compile debugging purposes.
radu
On 08/06/2012 04:46 PM, Wolfgang Denk wrote:
> Dear Radu,
>
> In message <501FC96A.8000400@intel.com> you wrote:
>> in the new shell
>>
>> >make coreboot-x86 (without _config)
>>
>> The output I got is as follows:
>>
>> Configuring for coreboot-x86 - Board: coreboot, Options:
>> SYS_TEXT_BASE=0xFC0000
>> make
>> /bin/bash: i386-linux-gcc: command not found
>> /bin/bash: i386-linux-gcc: command not found
> It seems CROSS_COMPILE is set to "i386-linux-", but i386-linux-gcc is
> not anywhere in your PATH. Please check your PATH and fix it.
>
> Best regards,
>
> Wolfgang Denk
>
[-- Attachment #2: Type: text/html, Size: 1773 bytes --]
next prev parent reply other threads:[~2012-08-06 14:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 12:38 [PATCH][RFC] u-boot: Upgrade to upstream stable 2012.07 Radu Moisan
2012-08-03 12:46 ` Martin Jansa
2012-08-03 14:45 ` Radu Moisan
2012-08-03 16:19 ` Wolfgang Denk
2012-08-06 6:28 ` Radu Moisan
2012-08-06 7:45 ` Wolfgang Denk
2012-08-06 13:40 ` Radu Moisan
2012-08-06 13:46 ` Wolfgang Denk
2012-08-06 14:09 ` Radu Moisan [this message]
2012-08-06 14:13 ` Wolfgang Denk
2012-08-07 2:58 ` Khem Raj
2012-08-07 5:50 ` Radu Moisan
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=501FD013.5040000@intel.com \
--to=radu.moisan@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=wd@denx.de \
/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