From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/3] libglib2: backport upstream patch to handle missing fcntl() flags
Date: Tue, 31 Jul 2018 21:43:15 +0200 [thread overview]
Message-ID: <20180731214315.4542df50@windsurf> (raw)
In-Reply-To: <20180730220218.26454-1-hollis_blanchard@mentor.com>
Hello,
On Mon, 30 Jul 2018 15:02:16 -0700, Hollis Blanchard wrote:
> On RHEL6 hosts, fcntl.h doesn't define F_SETPIPE_SZ or F_GETPIPE_SZ. Upstream
> glib has a patch for this case that wasn't applied to their 2.56.1 branch.
>
> Signed-off-by: Hollis Blanchard <hollis_blanchard@mentor.com>
> ---
> ...-fix-compilation-without-F_-S-G-ETPIPE_SZ.patch | 52 ++++++++++++++++++++++
> 1 file changed, 52 insertions(+)
> create mode 100644 package/libglib2/0005-gio-fix-compilation-without-F_-S-G-ETPIPE_SZ.patch
Applied to master after adding a reference to the autobuilder failure
being fixed. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-07-31 19:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 22:02 [Buildroot] [PATCH v2 1/3] libglib2: backport upstream patch to handle missing fcntl() flags Hollis Blanchard
2018-07-30 22:02 ` [Buildroot] [PATCH v2 2/3] host-attr: build fix for GCC <4.5 Hollis Blanchard
2018-07-31 19:47 ` Thomas Petazzoni
2018-07-30 22:02 ` [Buildroot] [PATCH v2 3/3] host-acl: build fix for GCC 4.4.7 Hollis Blanchard
2018-07-31 19:50 ` Thomas Petazzoni
2018-07-31 19:43 ` Thomas Petazzoni [this message]
2018-08-20 20:32 ` [Buildroot] [PATCH v2 1/3] libglib2: backport upstream patch to handle missing fcntl() flags 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=20180731214315.4542df50@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.