From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your build results for 2017-05-02
Date: Thu, 4 May 2017 09:57:50 +0200 [thread overview]
Message-ID: <20170504095750.7cb38619@free-electrons.com> (raw)
In-Reply-To: <035B547B-A554-4715-A235-95E6A1E14EE9@uclibc-ng.org>
Hello,
On Thu, 4 May 2017 09:48:57 +0200, Waldemar Brodkorb wrote:
> I wouldn't say it was wrong.
> We have all internal toolchains fixed and we get a good idea about the quality of the latest release.
>
> May be it will motivate Synopsis to release a new tarball, as other important ARC Bugfixes are included
> in this release.
Well the problem is that in the mean time, we have autobuilder failures
caused by this. We are about to release -rc1, so we will try to reduce
the number of autobuilder failures, and this will get in the way. Which
is why we need to find a solution here.
Options:
(1) Synopsys quickly publishes a new pre-built toolchain with uClibc
1.0.24 + wordexp
(2) We disable the Synopsys toolchain from our autobuilders
(3) We re-add exceptions in the relevant packages, but only for the
Synopsys toolchain (and not uClibc globally)
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-05-04 7:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170503062809.135BB207F9@mail.free-electrons.com>
[not found] ` <CAOMZO5B9sPeE+_YH4nWykogzB_dq7XUpz0AraMXjgazZjA_DxA@mail.gmail.com>
[not found] ` <CAOMZO5BbPjn9b6i1uDr01ikFsSHWy9xkzfpk7F7GhssQyCuuJw@mail.gmail.com>
2017-05-04 7:30 ` [Buildroot] [autobuild.buildroot.net] Your build results for 2017-05-02 Thomas Petazzoni
[not found] ` <035B547B-A554-4715-A235-95E6A1E14EE9@uclibc-ng.org>
2017-05-04 7:57 ` Thomas Petazzoni [this message]
2017-05-04 8:46 ` Peter Korsgaard
2017-05-04 15:34 ` Alexey Brodkin
2017-05-04 15:46 ` Thomas Petazzoni
2017-05-04 15:57 ` Alexey Brodkin
2017-05-04 19:04 ` Thomas Petazzoni
2017-05-04 19:28 ` Alexey Brodkin
2017-05-04 15:04 ` Thomas Petazzoni
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=20170504095750.7cb38619@free-electrons.com \
--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