From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH 1/1] iputils: Bump to version s20190324
Date: Tue, 7 May 2019 22:40:38 +0200 [thread overview]
Message-ID: <20190507224038.0e11b51b@windsurf> (raw)
In-Reply-To: <20190505232923.22744-1-petr.vorel@gmail.com>
Hello Petr,
On Mon, 6 May 2019 01:29:23 +0200
Petr Vorel <petr.vorel@gmail.com> wrote:
> I'm trying to update iputils for Buildroot to newest version s20190324,
> which changed build system to Meson. I cannot figure out which compiler
> option is missing / wrong, or which dependency is missing or which
> buildroot config is missing wrong. Any tip / idea?
ping6_common.c lacks:
#include <stddef.h>
once added, it builds fine. The installation then fails because:
define IPUTILS_INSTALL_TARGET_CMDS
$(INSTALL) -D -m 755 $(@D)/arping $(TARGET_DIR)/sbin/arping
$(INSTALL) -D -m 755 $(@D)/clockdiff $(TARGET_DIR)/bin/clockdiff
$(INSTALL) -D -m 755 $(@D)/ping $(TARGET_DIR)/bin/ping
$(INSTALL) -D -m 755 $(@D)/rarpd $(TARGET_DIR)/sbin/rarpd
$(INSTALL) -D -m 755 $(@D)/rdisc $(TARGET_DIR)/sbin/rdisc
$(INSTALL) -D -m 755 $(@D)/tftpd $(TARGET_DIR)/usr/sbin/in.tftpd
$(INSTALL) -D -m 755 $(@D)/tracepath $(TARGET_DIR)/bin/tracepath
$(INSTALL) -D -m 755 $(@D)/traceroute6 $(TARGET_DIR)/bin/traceroute6
endef
is no longer correct, as binaries are now produced in $(@D)/build/. But
probably we could use the standard installation procedure of the meson
build system instead of having custom install commands ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-05-07 20:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-05 23:29 [Buildroot] [RFC PATCH 1/1] iputils: Bump to version s20190324 Petr Vorel
2019-05-07 20:40 ` Thomas Petazzoni [this message]
[not found] ` <CAG27Bk2yCdpQAw5pEmZjwTs=WDn93Y7XUs0Yy7Wg9JAT+OmLkg@mail.gmail.com>
2019-05-08 19:46 ` Petr Vorel
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=20190507224038.0e11b51b@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.