From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2 1/4] toolchain/helpers: don't use the x$(...) = x"value" syntax
Date: Wed, 17 Jul 2013 19:00:51 +0200 [thread overview]
Message-ID: <20130717170051.GA3385@free.fr> (raw)
In-Reply-To: <1374048801-7666-2-git-send-email-thomas.petazzoni@free-electrons.com>
Thomas, All,
On 2013-07-17 10:13 +0200, Thomas Petazzoni spake thusly:
> As noted by Yann E. Morin, the x$(...) = x"value" syntax is old and
> ugly, and the easier to read "$(...)" = "value" can now be used
> without problems.
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
> toolchain/helpers.mk | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/toolchain/helpers.mk b/toolchain/helpers.mk
> index 95217e7..94fe015 100644
> --- a/toolchain/helpers.mk
> +++ b/toolchain/helpers.mk
> @@ -181,7 +181,7 @@ create_lib64_symlinks = \
> # $2: feature description
> #
> check_glibc_feature = \
> - if [ x$($(1)) != x"y" ] ; then \
> + if [ "$($(1))" != "y" ] ; then \
> echo "$(2) available in C library, please enable $(1)" ; \
> exit 1 ; \
> fi
> @@ -236,11 +236,11 @@ check_glibc = \
> #
> check_uclibc_feature = \
> IS_IN_LIBC=`grep -q "\#define $(1) 1" $(3) && echo y` ; \
> - if [ x$($(2)) != x"y" -a x$${IS_IN_LIBC} = x"y" ] ; then \
> + if [ "$($(2))" != "y" -a $${IS_IN_LIBC} = "y" ] ; then \
^^^^^^^^^^^^^^
You'd have to quote this, too, since it can be the empty string.
> echo "$(4) available in C library, please enable $(2)" ; \
> exit 1 ; \
> fi ; \
> - if [ x$($(2)) = x"y" -a x$${IS_IN_LIBC} != x"y" ] ; then \
> + if [ "$($(2))" = "y" -a $${IS_IN_LIBC} != "y" ] ; then \
^^^^^^^^^^^^^^
Ditto.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2013-07-17 17:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-17 8:13 [Buildroot] [PATCHv2 0/4] EABI vs EABIhf check Thomas Petazzoni
2013-07-17 8:13 ` [Buildroot] [PATCHv2 1/4] toolchain/helpers: don't use the x$(...) = x"value" syntax Thomas Petazzoni
2013-07-17 17:00 ` Yann E. MORIN [this message]
2013-07-17 8:13 ` [Buildroot] [PATCHv2 2/4] toolchain: check ARM EABI vs. EABIhf for external toolchains Thomas Petazzoni
2013-07-17 17:04 ` Yann E. MORIN
2013-07-17 8:13 ` [Buildroot] [PATCHv2 3/4] toolchain/toolchain-external: don't use x$(...) construct or == Thomas Petazzoni
2013-07-17 17:07 ` Yann E. MORIN
2013-07-17 8:13 ` [Buildroot] [PATCHv2 4/4] arch/arm: update VFPv2 comment to mention ARMv5 Thomas Petazzoni
2013-07-17 17:09 ` Yann E. MORIN
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=20130717170051.GA3385@free.fr \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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