From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] WIP: glibc 2.16 bump
Date: Sat, 12 Aug 2017 13:46:41 +0200 [thread overview]
Message-ID: <20170812134641.7895db19@windsurf> (raw)
In-Reply-To: <a24db610-bef2-c2fc-c9af-ba23cf29cc25@gmail.com>
Hello,
On Sat, 12 Aug 2017 12:24:50 +0200, Romain Naour wrote:
> I started to look at glibc 2.26 bump.
Good!
> All patches are uptream but the bump trigger some build issue with gcc 7 (older
> gcc version are not tested yet).
> For now I'm building only the toolchain on several arch, so no runtime test yet.
> How the freeelectron farm can help to test new gcc/libc version ?
If you submit the patch and/or push it to some branch somewhere, I can
apply it on a branch (not to the official Buildroot tree), and run a
test build of all the toolchains configurations, and give you the link
to the Gitlab CI build results.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-08-12 11:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-12 10:24 [Buildroot] WIP: glibc 2.16 bump Romain Naour
2017-08-12 11:46 ` Thomas Petazzoni [this message]
2017-08-12 13:04 ` Romain Naour
2017-08-14 13:04 ` Romain Naour
2017-08-14 14:24 ` Thomas Petazzoni
2017-08-14 14:44 ` Romain Naour
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=20170812134641.7895db19@windsurf \
--to=thomas.petazzoni@free-electrons.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