From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] trinity: fix build with kernel headers v4.19
Date: Thu, 13 Dec 2018 21:15:39 +0100 [thread overview]
Message-ID: <20181213211539.5b63a6cd@windsurf> (raw)
In-Reply-To: <8e600f4b5c8ef661080050b5b3af7e8ec9b8744a.1544641625.git.baruch@tkos.co.il>
Hello,
On Wed, 12 Dec 2018 21:07:05 +0200, Baruch Siach wrote:
> Kernel v4.19 introduced a change in linux/rds.h UAPI header that causes
> networking definitions collision with libc headers. Add a patch fixing
> that be reordering the include list.
>
> Fixes:
> http://autobuild.buildroot.net/results/b30/b30993de10c909602ec2e9098a91e400fa9c91f6/
> http://autobuild.buildroot.net/results/96d/96deb94e5f959c844060d449fae5668c5f3c5571/
> http://autobuild.buildroot.net/results/c7a/c7aa75fd8faad7ac49492497807d1a7fe4c4f955/
>
> Cc: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> ...s-include-libc-network-headers-first.patch | 48 +++++++++++++++++++
> 1 file changed, 48 insertions(+)
> create mode 100644 package/trinity/0006-proto-rds-include-libc-network-headers-first.patch
Applied to master after renumbering from 0006 to 0005 because there was
no 0005 patch. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-12-13 20:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 19:07 [Buildroot] [PATCH] trinity: fix build with kernel headers v4.19 Baruch Siach
2018-12-13 20:15 ` 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=20181213211539.5b63a6cd@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox