From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/x11r7/xserver_xorg-server: Fix ARM build
Date: Mon, 11 Nov 2019 15:36:57 +0100 [thread overview]
Message-ID: <20191111153657.1a56760e@windsurf.home> (raw)
In-Reply-To: <20191111124807.1151582-1-thomas.preston@codethink.co.uk>
Hello Thomas,
On Mon, 11 Nov 2019 12:48:07 +0000
Thomas Preston <thomas.preston@codethink.co.uk> wrote:
> The ARM sys/io.h has been removed from upstream glibc, which is in
> buildroot. This causes the xorg-server build to fail on ARM when using
> the glibc toolchain.
>
> The following patches from upstream xserver fix this, but have not yet
> been released.
>
> Signed-off-by: Thomas Preston <thomas.preston@codethink.co.uk>
Do we have any autobuilder failures for this? From a quick look, I
don't see any. So the question is: why?
> diff --git a/package/x11r7/xserver_xorg-server/1.20.5/0006-compiler.h-only-use-inx-outx-on-ARM-with-glibc.patch b/package/x11r7/xserver_xorg-server/1.20.5/0006-compiler.h-only-use-inx-outx-on-ARM-with-glibc.patch
> new file mode 100644
> index 0000000000..f1b27d7484
> --- /dev/null
> +++ b/package/x11r7/xserver_xorg-server/1.20.5/0006-compiler.h-only-use-inx-outx-on-ARM-with-glibc.patch
> @@ -0,0 +1,32 @@
> +From 6a2ce6c5da9456b97683db6224f38ef3b02cce4b Mon Sep 17 00:00:00 2001
> +From: Ross Burton <ross.burton@intel.com>
> +Date: Thu, 20 Sep 2018 13:21:34 +0100
> +Subject: [PATCH 1/2] compiler.h: only use inx/outx on ARM with glibc
Use "git format-patch -N" when generating patches, so that we don't
have the "PATCH 1/2" prefix, but just "PATCH". Indeed PATCH 1/2 for a
patch labeled 0006-something is a bit useless.
> +
> +musl only implements inx/outx on x86, so check for __GLIBC__ instead of
> +__linux__.
> +
> +Signed-off-by: Ross Burton <ross.burton@intel.com>
But this commit doesn't seem at all related to the glibc failure, it
would rather be useful to fix a build issue against the musl C library.
I also don't see such build failures in our autobuilders. Why?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-11-11 14:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 12:48 [Buildroot] [PATCH] package/x11r7/xserver_xorg-server: Fix ARM build Thomas Preston
2019-11-11 14:36 ` Thomas Petazzoni [this message]
2019-11-11 15:06 ` Thomas Preston
2019-11-11 17:12 ` Thomas Preston
2019-11-12 20:24 ` Thomas Petazzoni
2019-11-13 10:39 ` Thomas Preston
2019-11-13 10:51 ` Thomas Petazzoni
2019-11-17 17:08 ` Arnout Vandecappelle
2019-11-13 11:10 ` Romain Naour
2019-11-13 12:06 ` Thomas Petazzoni
2019-11-13 12:32 ` Romain Naour
2019-11-13 12:39 ` Thomas Petazzoni
2019-11-12 19:05 ` Peter Seiderer
2019-11-12 19:20 ` Peter Seiderer
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=20191111153657.1a56760e@windsurf.home \
--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