From: "Måns Rullgård" <mans@mansr.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] env: Fix operation of 'make environ'
Date: Mon, 28 Aug 2017 12:01:51 +0100 [thread overview]
Message-ID: <yw1x8ti43qhs.fsf@mansr.com> (raw)
In-Reply-To: <20170827164850.31986-1-sjg@chromium.org> (Simon Glass's message of "Sun, 27 Aug 2017 10:48:47 -0600")
Simon Glass <sjg@chromium.org> writes:
> This was broken by the recent environment refactoring. Specifically:
>
> $ make environ
> scripts/Makefile.build:59: tools/environ/Makefile: No such file or directory
> make[1]: *** No rule to make target 'tools/environ/Makefile'. Stop.
> make: *** [Makefile:1469: environ] Error 2
>
> Fix this by updating the Makefile and adjusting the #include filesnames in
> two C files.
>
> Fixes: ec74f5f (Makefile: Rename 'env' target to 'environ')
> Reported-by: M책ns Rullg책rd <mans@mansr.com>
> Signed-off-by: Simon Glass <sjg@chromium.org>
> ---
>
> Makefile | 2 +-
> tools/env/env_attr.c | 2 +-
> tools/env/env_flags.c | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
This still breaks any build scripts using the old target (yes, there are
many). That's probably acceptable, but a mention of it in some release
note would be nice.
Come to think of it, if we're anyway going to break things, how about
giving that target a more descriptive name than environ? I suggest
envtools.
> diff --git a/Makefile b/Makefile
> index a0f3bfd2a52..dd9d5678118 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -1466,7 +1466,7 @@ checkarmreloc: u-boot
> fi
>
> environ: scripts_basic
> - $(Q)$(MAKE) $(build)=tools/$@
> + $(Q)$(MAKE) $(build)=tools/env
>
> tools-only: scripts_basic $(version_h) $(timestamp_h)
> $(Q)$(MAKE) $(build)=tools
> diff --git a/tools/env/env_attr.c b/tools/env/env_attr.c
> index 502d4c900bf..4d8536335c3 100644
> --- a/tools/env/env_attr.c
> +++ b/tools/env/env_attr.c
> @@ -1 +1 @@
> -#include "../../common/env_attr.c"
> +#include "../../env/attr.c"
> diff --git a/tools/env/env_flags.c b/tools/env/env_flags.c
> index b261cb8e390..71e13e2021f 100644
> --- a/tools/env/env_flags.c
> +++ b/tools/env/env_flags.c
> @@ -1 +1 @@
> -#include "../../common/env_flags.c"
> +#include "../../env/flags.c"
> --
> 2.14.1.342.g6490525c54-goog
>
--
M책ns Rullg책rd
next prev parent reply other threads:[~2017-08-28 11:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-27 16:48 [U-Boot] [PATCH] env: Fix operation of 'make environ' Simon Glass
2017-08-28 11:01 ` Måns Rullgård [this message]
2017-08-28 11:13 ` Tom Rini
2017-08-28 16:08 ` Joe Hershberger
2017-09-05 7:54 ` Simon Glass
-- strict thread matches above, loose matches on Subject: below --
2017-08-29 19:53 Simon Glass
2017-08-29 20:02 ` Joe Hershberger
2017-08-29 20:16 ` Simon Glass
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=yw1x8ti43qhs.fsf@mansr.com \
--to=mans@mansr.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