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 19:28:45 +0000	[thread overview]
Message-ID: <1493926124.7376.22.camel@synopsys.com> (raw)
In-Reply-To: <20170504210431.4ac7b1ec@free-electrons.com>

Hi Thomas,

On Thu, 2017-05-04 at 21:04 +0200, Thomas Petazzoni wrote:
> Hello,
> 
> On Thu, 4 May 2017 15:57:03 +0000, Alexey Brodkin wrote:
> 
> > 
> > > 
> > > Sorry, but I don't understand what you suggested here. In the light of
> > > my explanation above, could you clarify what you mean by "ARC prebuilt
> > > tools" ???
> > 
> > Scratch it then :)
> > 
> > If ARC prebuilt tools are not used by BR autobuilder there's no sense in
> > touching packages affected by these tools.
> 
> I have fixed the br-arcle-hs38.config to really use the pre-built
> toolchain generated by Buildroot:

Thanks for doing that!

> So the Synopsys ARC toolchain will no longer be tested by our
> autobuilders.

That's fine.

-Alexey

  reply	other threads:[~2017-05-04 19:28 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
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 [this message]
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=1493926124.7376.22.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