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 09:28:15 +0300 [thread overview]
Message-ID: <501F63FF.1070401@intel.com> (raw)
In-Reply-To: <20120803161915.399D1203B3D@gemini.denx.de>
On 08/03/2012 07:19 PM, Wolfgang Denk wrote:
> Dear Radu Moisan,
>
> In message <1343997523-4117-1-git-send-email-radu.moisan@intel.com> you wrote:
>> Building u-boot requires UBOOT_MACHINE. In the u-boot README file
>> building u-boot is achieved with "make NAME_config" and then
>> "make all". I assumend UBOOT_MACHINE to be the "NAME" part and thus,
> Actually a plain
>
> make NAME
>
> does the same as "make NAME_config && make all".
>
> You might also consider running "./MAKEALL NAME" instead, which
> aut-adjusts to te number of available cores on the build host, so you
> get somewhat reduced build times.
I've tried to build this way but got into some errors and did not
pursued further in debugging them. However, because UBOOT_MACHINE is
already used as NAME_config, would be difficult to change it to NAME and
ask everyone who use it, to switch. I will go with current configuration
"make NAME_config" & "make all"
radu
next prev parent reply other threads:[~2012-08-06 6:38 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 [this message]
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
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=501F63FF.1070401@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 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.