From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] make clean problem
Date: Wed, 08 Oct 2008 14:08:46 -0400 [thread overview]
Message-ID: <48ECF72E.20704@ge.com> (raw)
In-Reply-To: <20081008152657.DD71D8356979@gemini.denx.de>
Wolfgang Denk wrote:
> Dear "Eugene O'Brien",
>
> In message <8B3930FEA8618C44B48EB06B5D33A06E01CCE207@satmail.Advantech.ca> you wrote:
>> @rm -f $(obj)tools/env/{fw_printenv,fw_setenv}
>>
>> The reason is (after scratching my head for a few hours) that on my
>> platform BASH is not the default shell. I am using Ubuntu and /bin/sh is
>> linked to dash (see https://wiki.ubuntu.com/DashAsBinSh for details). As
>> I am not an expert on shells, my guess is that the above construct is a
>> "bashism" and not compliant to /bin/sh.
>
> Good catch...
>
>> There are two trivial solutions to this problem:
>>
>> (a) Add a line SHELL=/bin/bash somewhere in top level Makefile
>> (b) Write out each individual file's path name separately in the @rm
>> command line.
>
> I think the above way to abbreviate long lists of file names that
> have a long common partis pretty useful to keep the code readable, so
> I tend to prefer solution (a).
>
> But let's see what other people say...
I *LIKE* bash, so I too like (a).
Having said that, and with the disclaimer that I'm not sure it is an
improvement, I believe the following line is a "make-ism" equivalent to
the bash-ism (untested):
@rm -f $(foreach file, fw_printenv fw_setenv, $(obj)tools/env/$(file))
> Best regards,
>
> Wolfgang Denk
Ditto,
gvb
next prev parent reply other threads:[~2008-10-08 18:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 13:52 [U-Boot] make clean problem Eugene O'Brien
2008-10-08 15:26 ` Wolfgang Denk
2008-10-08 18:08 ` Jerry Van Baren [this message]
2008-10-08 19:13 ` Wolfgang Denk
[not found] ` <d66caabb0810081414y21152e4cw67a268d385dde4b7@mail.gmail.com>
2008-10-08 21:16 ` Graeme Russ
2008-10-08 22:09 ` Wolfgang Denk
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=48ECF72E.20704@ge.com \
--to=gerald.vanbaren@ge.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 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.