From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] MAKEALL: Fix case substitution for old bash
Date: Thu, 21 Mar 2013 13:38:37 -0700 [thread overview]
Message-ID: <514B6FCD.9060703@freescale.com> (raw)
In-Reply-To: <20130321202835.GA2575@badger>
On 03/21/2013 01:28 PM, Allen Martin wrote:
> On Thu, Mar 21, 2013 at 12:58:15PM -0700, York Sun wrote:
>> Bash ver 3.x doesn't support the parameter expansion with case
>> substitution. Use tr instead.
>>
>> Signed-off-by: York Sun <yorksun@freescale.com>
>> ---
>> I am not sure if using 'tr' is a good idea. Any suggestion is welcomed.
>>
>> MAKEALL | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/MAKEALL b/MAKEALL
>> index c1d8957..ac92ef6 100755
>> --- a/MAKEALL
>> +++ b/MAKEALL
>> @@ -664,7 +664,7 @@ build_target() {
>> export BUILD_DIR="${output_dir}"
>>
>> target_arch=$(get_target_arch ${target})
>> - eval cross_toolchain=\$CROSS_COMPILE_${target_arch^^}
>> + eval cross_toolchain=\$CROSS_COMPILE_`echo $target_arch | tr '[:lower:]' '[:upper:]'`
>
> Looks fine to me. I'm not sure if there's a preference between using
> backtick or $() for shell commands, it looks like both are used in the
> script.
Let's wait for others to chime in.
>
>> if [ "${cross_toolchain}" ] ; then
>> MAKE="make CROSS_COMPILE=${cross_toolchain}"
>> elif [ "${CROSS_COMPILE}" ] ; then
>> --
>> 1.7.9.5
>>
>>
>
> PS: What happened with your bool fixup patch? I'm a big fan of that
> patch :^)
>
Tom asked on March 4th. I think he will accept it.
York
next prev parent reply other threads:[~2013-03-21 20:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 19:58 [U-Boot] [RFC] MAKEALL: Fix case substitution for old bash York Sun
2013-03-21 20:28 ` Allen Martin
2013-03-21 20:38 ` York Sun [this message]
2013-03-27 19:55 ` Tom Rini
[not found] ` <5155C7C9.2010306@freescale.com>
[not found] ` <20130329172922.GA18937@badger>
[not found] ` <5155D412.1020802@freescale.com>
[not found] ` <20130329175205.GB18937@badger>
[not found] ` <5155D5D1.1000802@freescale.com>
[not found] ` <20130329180520.GA1867@badger>
2013-03-30 22:30 ` Simon Glass
2013-04-01 18:19 ` York Sun
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=514B6FCD.9060703@freescale.com \
--to=yorksun@freescale.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.