From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/x11r7/xserver_xorg-server: Fix ARM build
Date: Wed, 13 Nov 2019 11:51:15 +0100 [thread overview]
Message-ID: <20191113115115.40645a37@windsurf> (raw)
In-Reply-To: <77353588-bf06-8112-4afe-41f488dbaa66@codethink.co.uk>
On Wed, 13 Nov 2019 10:39:38 +0000
Thomas Preston <thomas.preston@codethink.co.uk> wrote:
> > So, when I say "autobuilders", I'm referring to (2) above. And I don't
> > get why this sys/io.h doesn't occur in the autobuilders.
>
> Got it, thanks. Is it possible to search the autobuilder configurations for
> the above case? Maybe it never came up. Or maybe it *has* been tested, just
> before this bug was introduced.
We do have an ARM toolchain configuration that builds an internal
Buildroot toolchain with glibc:
support/config-fragments/autobuild/br-arm-internal-glibc.config
So, I did a search with this:
http://autobuild.buildroot.net/index.php?arch=arm&symbols%5BBR2_TOOLCHAIN_BUILDROOT_GLIBC%5D=y&symbols%5BBR2_PACKAGE_XSERVER_XORG_SERVER%5D=y
And I can see:
http://autobuild.buildroot.net/results/b7c/b7c49525277ea1ccdd7011ab9295f6bf4050e4bb/build-end.log
which is exactly the build failure you're fixing. I'm not sure why it
didn't happen more often.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-11-13 10:51 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
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 [this message]
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=20191113115115.40645a37@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