From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Failure on attempt to build env tools
Date: Mon, 28 Apr 2014 11:57:16 +0200 [thread overview]
Message-ID: <201404281157.16534.marex@denx.de> (raw)
In-Reply-To: <1398678005.3429.10.camel@abrodkin-8560l.internal.synopsys.com>
On Monday, April 28, 2014 at 11:40:05 AM, Alexey Brodkin wrote:
> Hi Marek,
>
> I noticed you recently committed support of AES encryption in U-Boot
> tools here -
> http://git.denx.de/?p=u-boot.git;a=commit;h=a8a752c084031905940129f8a6ba303
> 925e0fac9
>
> And now I cannot build env tools.
>
> Here's how to reproduce my experience:
> ===============
> $ make yourboard_config
> $ make env
> make[1]: *** No rule to make target `tools/env/aes.c', needed by
> `tools/env/aes.o'. Stop.
> make: *** [env] Error 2
> ===============
>
> And from tools/env/Makefile I see that target "aes.o" exists while
> "aes.c" itself is situated in "./lib" folder.
>
> Could you please try to build env tools and if you see the same error
> could you please fix it?
It's here as well, must be some post-kbuild-migration problem. Patch is out.
+CC Masahiro-san .
btw. did you have time to look at my PCIe email please?
Best regards,
Marek Vasut
prev parent reply other threads:[~2014-04-28 9:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 9:40 [U-Boot] Failure on attempt to build env tools Alexey Brodkin
2014-04-28 9:57 ` Marek Vasut [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=201404281157.16534.marex@denx.de \
--to=marex@denx.de \
--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