From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Fix issue with printvars executing giant shell command
Date: Mon, 17 Sep 2018 21:54:37 +0200 [thread overview]
Message-ID: <20180917195437.GB21035@scaer> (raw)
In-Reply-To: <1537207369.7736.6.camel@impinj.com>
Trent, All,
On 2018-09-17 18:02 +0000, Trent Piepho spake thusly:
> On Mon, 2018-09-10 at 20:18 +0200, Yann E. MORIN wrote:
> > In a recipe, a command line that contains only spaces will not be executed
> > by make.
[--SNIP--]
> Ok, if you like that better. My thought was "strip eats whitespace" is
> simple, but "a recipe line starting with a tab and containing only
> whitespace is skipped" is more obscure. In fact, while it does appear
> to be true, I haven't found anything in the make docs clearly stating
> this.
From the make manual, chapter 5.1, "Recipe Syntax" [0], states:
* A blank line that begins with a tab is not blank: it?s an empty
recipe (see Empty Recipes).
... where "Empty Recipes" is a link to chapter 5.9, titled "Using
Empty Recipes" [1], which starts with:
It is sometimes useful to define recipes which do nothing. This
is done simply by giving a recipe that consists of nothing but
whitespace.
[0] https://www.gnu.org/software/make/manual/make.html#Recipe-Syntax
[1] https://www.gnu.org/software/make/manual/make.html#Empty-Recipes
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. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2018-09-17 19:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 23:15 [Buildroot] [PATCH] Fix issue with printvars executing giant shell command Trent Piepho
2018-08-29 20:49 ` Yann E. MORIN
2018-09-10 17:45 ` Trent Piepho
2018-09-10 18:18 ` Yann E. MORIN
2018-09-17 18:02 ` Trent Piepho
2018-09-17 19:54 ` Yann E. MORIN [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=20180917195437.GB21035@scaer \
--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