Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your build results for 2017-05-02
Date: Thu, 4 May 2017 15:34:55 +0000	[thread overview]
Message-ID: <1493912093.7376.14.camel@synopsys.com> (raw)
In-Reply-To: <87r305au17.fsf@dell.be.48ers.dk>

Hi Thomas, Peter, Waldemar, all,

On Thu, 2017-05-04 at 10:46 +0200, Peter Korsgaard wrote:
> > 
> > > 
> > > > 
> > > > > 
> > > > > > 
> > > > > > "Thomas" == Thomas Petazzoni <thomas.petazzoni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org> writes:
> 
> ?> 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

Unfortunately in the beginning of the current toolchain development cycle
we decided to stay on uClibc-ng 1.0.17 + backported ARC-related patches
due to different reasons and given we're now on rc2 stage there's no chance
to switch to any other version unfortunately. I hope next dev cycle we'll use just
latest upstream uClibc-ng release.

In other words (1) won't happen in coming days.
> 
> ?>??(2) We disable the Synopsys toolchain from our autobuilders

We're talking only about __prebuilt__ ARC toolchain right?
Because Buildroot-built tools use latest uClibc-ng with correct config.

Ideally I'd prefer to update affected packages so they are disabled for
ARC prebuilt tools with some easily greppable comment like:
----------------->8-----------------
?xxx yyy zzz # arc_prebuilt lacks wordexp
----------------->8-----------------
that will help us to track missing parts we need to work on in the future.
Otherwise we may just disable autobuilder for ARC prebuilt tools because:

1) There's no such thing as prebuilt engineering builds i.e. autobuilder
? ?only will test either RCs or final releases of ARC prebuilt tools which
? ?IMHO makes not much sense as that's a bit too late, rgiht?

2) We know there're differences in ARC prebuilt tools from what gets built in
? ?Buildroot still having ARC prebuilt tools is a nice opportunity to
? ?simplify life for some people who prefers to not build toolchain
? ?themselves and for basic stuff it usually works quite fine.

-Alexey

  reply	other threads:[~2017-05-04 15:34 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
2017-05-04  8:46           ` Peter Korsgaard
2017-05-04 15:34             ` Alexey Brodkin [this message]
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=1493912093.7376.14.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.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