From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH-for-master 2/2] package/iproute2: backport patch to fix compilation under glibc < 2.18
Date: Mon, 25 Feb 2019 22:14:33 +0100 [thread overview]
Message-ID: <20190225211431.GA28518@x230> (raw)
In-Reply-To: <20190225211147.14947-3-patrickdepinguin@gmail.com>
Hi Thomas,
> From: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
> When compiling iproute2 using a toolchain containing glibc 2.17 and older, it fails due to a missing definition of AF_VSOCK.
> Add a submitted and accepted upstream patch to fix this issue.
> Signed-off-by: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
Reviewed-by: Petr Vorel <petr.vorel@gmail.com>
Thanks for your fix!
Kind regards,
Petr
next prev parent reply other threads:[~2019-02-25 21:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 21:11 [Buildroot] [PATCH-for-master 0/2] misc fixes for 2019.02 Thomas De Schampheleire
2019-02-25 21:11 ` [Buildroot] [PATCH-for-master 1/2] package/meson: don't install cross-compilation.conf during target-finalize Thomas De Schampheleire
2019-02-26 18:52 ` Peter Korsgaard
2019-02-26 19:48 ` Thomas De Schampheleire
2019-02-27 17:18 ` Thomas Petazzoni
2019-02-27 19:57 ` Thomas De Schampheleire
2019-03-17 15:23 ` Thomas Petazzoni
2019-03-25 9:47 ` Thomas De Schampheleire
2019-10-27 13:34 ` Arnout Vandecappelle
2019-02-25 21:11 ` [Buildroot] [PATCH-for-master 2/2] package/iproute2: backport patch to fix compilation under glibc < 2.18 Thomas De Schampheleire
2019-02-25 21:14 ` Petr Vorel [this message]
2019-02-25 21:31 ` Thomas Petazzoni
2019-03-16 21:36 ` 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=20190225211431.GA28518@x230 \
--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