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 13:06:30 +0100 [thread overview]
Message-ID: <20191113130630.759bf8de@windsurf> (raw)
In-Reply-To: <1debcd70-de93-f709-a313-f358572c3048@smile.fr>
Hello,
On Wed, 13 Nov 2019 12:10:34 +0100
Romain Naour <romain.naour@smile.fr> wrote:
> @Thomas Petazzoni: Maybe we need to rebuild the arm bleeding edge toolchain used
> by the autobuilders using the current glibc version (2.30).
True.
> The current prebuilt toolchain are from 06/2019 but glibc 2.30 has been released
> 08/2019.
>
> There is only one internal toolchain for arm and it use uclibc-ng by default.
>
> Maybe we can add a new internal toolchain for glibc and musl ?
We already have these:
$ ls -1 support/config-fragments/autobuild/br-arm-internal-*
support/config-fragments/autobuild/br-arm-internal-full.config
support/config-fragments/autobuild/br-arm-internal-glibc.config
support/config-fragments/autobuild/br-arm-internal-musl.config
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-11-13 12:06 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
2019-11-17 17:08 ` Arnout Vandecappelle
2019-11-13 11:10 ` Romain Naour
2019-11-13 12:06 ` Thomas Petazzoni [this message]
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=20191113130630.759bf8de@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.