From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 3/3] package/iputils: create ping6 symlink in post install target hook
Date: Wed, 19 Jun 2019 23:30:08 +0200 [thread overview]
Message-ID: <20190619213008.7883-3-petr.vorel@gmail.com> (raw)
In-Reply-To: <20190619213008.7883-1-petr.vorel@gmail.com>
Upstream expect distros will do it, see
https://github.com/iputils/iputils/commit/ebad35fee3de851b809c7b72ccc654a72b6af61d
Signed-off-by: Petr Vorel <petr.vorel@gmail.com>
---
Changes v1->v2:
* Use IPUTILS_POST_INSTALL_TARGET_HOOKS (previously it
IPUTILS_POST_INSTALL_HOOKS was used). IPUTILS_POST_INSTALL_TARGET_HOOKS
works, but not really sure which one is correct/more suitable.
Kind regards,
Petr
package/iputils/iputils.mk | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/package/iputils/iputils.mk b/package/iputils/iputils.mk
index c6f380a84a..f62b027894 100644
--- a/package/iputils/iputils.mk
+++ b/package/iputils/iputils.mk
@@ -65,6 +65,12 @@ define IPUTILS_MOVE_BINARIES
endef
IPUTILS_POST_INSTALL_TARGET_HOOKS += IPUTILS_MOVE_BINARIES
+# upstream requires distros to create symlink
+define IPUTILS_CREATE_PING6_SYMLINK
+ln -sv $(TARGET_DIR)/bin/ping $(TARGET_DIR)/bin/ping6
+endef
+IPUTILS_POST_INSTALL_TARGET_HOOKS += IPUTILS_CREATE_PING6_SYMLINK
+
# handle permissions ourselves
IPUTILS_CONF_OPTS += -DNO_SETCAP_OR_SUID=true
define IPUTILS_PERMISSIONS
--
2.21.0
next prev parent reply other threads:[~2019-06-19 21:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 21:30 [Buildroot] [PATCH v2 1/3] package/iputils: Reenable traceroute6 Petr Vorel
2019-06-19 21:30 ` [Buildroot] [PATCH v2 2/3] iputils: Update upstream status on patches Petr Vorel
2019-06-22 8:06 ` Thomas Petazzoni
2019-06-19 21:30 ` Petr Vorel [this message]
2019-06-22 8:08 ` [Buildroot] [PATCH v2 3/3] package/iputils: create ping6 symlink in post install target hook Thomas Petazzoni
2019-06-22 8:06 ` [Buildroot] [PATCH v2 1/3] package/iputils: Reenable traceroute6 Thomas Petazzoni
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=20190619213008.7883-3-petr.vorel@gmail.com \
--to=petr.vorel@gmail.com \
--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