public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Aneesh V <aneesh@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Makefile: Add the missing dependency for spl target
Date: Fri, 18 Nov 2011 13:55:42 +0530	[thread overview]
Message-ID: <4EC61686.90300@ti.com> (raw)
In-Reply-To: <4EBBF690.4000603@ti.com>

Dear Wolfgang,

On Thursday 10 November 2011 09:36 PM, Aneesh V wrote:
> Hi Wolfgang,
>
> On Saturday 05 November 2011 01:13 PM, Aneesh V wrote:
>> Wolfgang's patch for build time improvement is bringing
>> out issues due to missing dependencies in the top-level
>> Makefile. I get errors such as the below while building
>> with many threads.
>>
>> make[1]: /home/a0393566local/u-boot-denx/tools/mkimage: Command not found
>
> Now that your build time improvement patch is up-stream omap and any
> other platform that uses any of the tools during SPL build may face
> occasional failures. Can you pull this one if my change looks ok?

Gentle reminder. If you don't have any objections to this one could you
consider pulling it. It avoids a build break.

br,
Aneesh

>
>>
>> This also allows one to do:
>> $ make spl/u-boot-spl.bin
>> if you want to build only spl
>>
>> Cc: Wolfgang Denk<wd@denx.de>
>> Signed-off-by: Aneesh V<aneesh@ti.com>
>> ---
>> Makefile | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/Makefile b/Makefile
>> index 82de62b..7ae8b22 100644
>> --- a/Makefile
>> +++ b/Makefile
>> @@ -481,7 +481,7 @@ mmc_spl: $(TIMESTAMP_FILE) $(VERSION_FILE) depend
>>
>> $(obj)mmc_spl/u-boot-mmc-spl.bin: mmc_spl
>>
>> -$(obj)spl/u-boot-spl.bin: depend
>> +$(obj)spl/u-boot-spl.bin: $(SUBDIR_TOOLS) depend
>> $(MAKE) -C spl all
>>
>> updater:
>

  reply	other threads:[~2011-11-18  8:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-05  7:43 [U-Boot] [PATCH] Makefile: Add the missing dependency for spl target Aneesh V
2011-11-10 16:06 ` Aneesh V
2011-11-18  8:25   ` Aneesh V [this message]
2011-11-18 16:16 ` Stefan Roese

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=4EC61686.90300@ti.com \
    --to=aneesh@ti.com \
    --cc=u-boot@lists.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