From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/3] package/iputils: Reenable traceroute6
Date: Sat, 22 Jun 2019 10:06:15 +0200 [thread overview]
Message-ID: <20190622100615.2f4502d9@windsurf> (raw)
In-Reply-To: <20190619213008.7883-1-petr.vorel@gmail.com>
On Wed, 19 Jun 2019 23:30:06 +0200
Petr Vorel <petr.vorel@gmail.com> wrote:
> Bump to s20190515 removed traceroute6 build (it's not built by default
> since this version in upstream). Reenable it again.
>
> Fixes: 9ffcd9279e ("package/iputils: bump to version s20190515")
>
> This requires fix similar to one in 0003-meson.build-fix-build-with-NLS.patch [1]
>
> traceroute6 is in /usr/sbin, so no need to handle busybox problem
> (6e18892733 "package/iputils: move binaries to the location also used by
> Busybox").
>
> [1] http://autobuild.buildroot.org/results/0a8a3efe734ac7fb3a68ba505277681857dc0a3d
>
> Suggested-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> Signed-off-by: Petr Vorel <petr.vorel@gmail.com>
> ---
> Changes v1->v2:
> * Fix traceroute6 path in IPUTILS_PERMISSIONS, it must be /usr/bin/traceroute6
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-06-22 8:06 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 ` [Buildroot] [PATCH v2 3/3] package/iputils: create ping6 symlink in post install target hook Petr Vorel
2019-06-22 8:08 ` Thomas Petazzoni
2019-06-22 8:06 ` Thomas Petazzoni [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=20190622100615.2f4502d9@windsurf \
--to=thomas.petazzoni@bootlin.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 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.