All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/x11r7/xserver_xorg-server: Fix ARM build
Date: Tue, 12 Nov 2019 21:24:46 +0100	[thread overview]
Message-ID: <20191112212446.21cbdbca@windsurf> (raw)
In-Reply-To: <08d749aa-743d-d05c-7aae-b98e70862617@codethink.co.uk>

Hello Thomas,

On Mon, 11 Nov 2019 17:12:13 +0000
Thomas Preston <thomas.preston@codethink.co.uk> wrote:

> I can reproduce with some changes to raspberrypi3_defconfig. The
> changes can be summarised as:
> - Switch glibc toolchain instead of uclibc
> - Enable xorg-server
> 
> I don't think there are any defconfigs (except with my changes) which
> meet these conditions:
> 
> 	$ git grep -l BR2_arm=y configs | xargs grep -l GLIBC | xargs grep XORG_SERVER
> 	configs/raspberrypi3_defconfig:BR2_PACKAGE_XSERVER_XORG_SERVER=y
> 
> So this condition is never reproduced in the autobuilder.

The autobuilders are completely unrelated to the defconfigs.

We have two completely distinct CI mechanisms:

 (1) Gitlab CI. This one does the kind of traditional CI that most
     projects have. In the case of Buildroot, it does build the defconfigs
     and runs the runtime tests on a regular basis.

 (2) Autobuilders. These generate random configurations, and build
     those random configurations. We have a number of machines (about
     5-6 machines) that do this 24/7 and report the results at
     http://autobuild.buildroot.org. This gives a much wider testing
     coverage than building defconfigs, as our defconfigs are almost all
     minimal.

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.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-11-12 20:24 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 [this message]
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=20191112212446.21cbdbca@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.