From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ifplugd: remove spurious newline excape
Date: Tue, 2 Dec 2014 09:00:24 +0200 [thread overview]
Message-ID: <20141202070024.GA2263@tarshish> (raw)
In-Reply-To: <fb06c6bb75e7486b104103ed0de58d64fa3f2058.1417503529.git.baruch@tkos.co.il>
Hi Buildroot list,
On Tue, Dec 02, 2014 at 08:58:49AM +0200, Baruch Siach wrote:
> Commit 5ad5d55924bcc (ifplugd: install configuration files unconditionally)
> removed the conditional configuration file install, but left an redundant
> newline escape, causing the following error:
>
> package/ifplugd/ifplugd.mk:23: *** missing 'endef', unterminated 'define'. Stop.
>
> Fix this.
In subject: s/excape/escape/
baruch
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> package/ifplugd/ifplugd.mk | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/package/ifplugd/ifplugd.mk b/package/ifplugd/ifplugd.mk
> index 03ed8cdf33a2..6b6141e7b8b3 100644
> --- a/package/ifplugd/ifplugd.mk
> +++ b/package/ifplugd/ifplugd.mk
> @@ -24,7 +24,7 @@ define IFPLUGD_INSTALL_FIXUP
> $(INSTALL) -D -m 0644 $(@D)/conf/ifplugd.conf $(TARGET_DIR)/etc/ifplugd/ifplugd.conf; \
> $(SED) 's^\(ARGS=.*\)w^\1^' $(TARGET_DIR)/etc/ifplugd/ifplugd.conf; \
> $(INSTALL) -D -m 0755 $(@D)/conf/ifplugd.action \
> - $(TARGET_DIR)/etc/ifplugd/ifplugd.action ; \
> + $(TARGET_DIR)/etc/ifplugd/ifplugd.action
> endef
>
> IFPLUGD_POST_INSTALL_TARGET_HOOKS += IFPLUGD_INSTALL_FIXUP
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2014-12-02 7:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 6:58 [Buildroot] [PATCH] ifplugd: remove spurious newline excape Baruch Siach
2014-12-02 7:00 ` Baruch Siach [this message]
2014-12-02 8:40 ` Peter Korsgaard
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=20141202070024.GA2263@tarshish \
--to=baruch@tkos.co.il \
--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