Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Radu Moisan <radu.moisan@intel.com>
To: 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: Tue, 07 Aug 2012 08:50:31 +0300	[thread overview]
Message-ID: <5020ACA7.4060500@intel.com> (raw)
In-Reply-To: <20120806141351.8D649203FD8@gemini.denx.de>

I meant, set with the correct value. "i386-linux-" is preloaded into 
CROSS_COMPILE and then at do_compile() "gcc" is appended to it.
Is there in interest, to actually build u-boot in devshell?

Radu

On 08/06/2012 05:13 PM, Wolfgang Denk wrote:
> Dear Radu,
>
> In message <501FD013.5040000@intel.com> you wrote:
>> 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.
> But CROSS_COMPILE _is_ set (and apparently has the value
> "i386-linux-".
>
> The problem is that PATH is not set such that it contains any such
> file as i386-linux-gcc.
>
>
> Best regards,
>
> Wolfgang Denk
>




      parent reply	other threads:[~2012-08-07  6:00 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
2012-08-06 14:13             ` Wolfgang Denk
2012-08-07  2:58               ` Khem Raj
2012-08-07  5:50               ` Radu Moisan [this message]

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=5020ACA7.4060500@intel.com \
    --to=radu.moisan@intel.com \
    --cc=openembedded-core@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