Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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:30:49 +0200	[thread overview]
Message-ID: <20170504093049.27618dbf@free-electrons.com> (raw)
In-Reply-To: <CAOMZO5BbPjn9b6i1uDr01ikFsSHWy9xkzfpk7F7GhssQyCuuJw@mail.gmail.com>

Hello,

On Wed, 3 May 2017 18:20:20 -0300, Fabio Estevam wrote:

> >>          arc | atest-895b0183a89c15f5e2305... | http://autobuild.buildroot.net/results/f344bbc94344107ef2f0337a4d8f211563d5a3bf

This one is the ARC pre-built toolchain, which we don't have control
over. So for now, we need to add an exclusion.

Waldemar: in fact, re-enabling atest, ifupdown and lvm on uClibc was
wrong, because the ARC external toolchain provided pre-built by
Synopsys does not have wordexp support and does not use uClibc-ng
1.0.24 yet.

Vlad: do you know when the Synopsys toolchain might be rebuilt with
those options enabled?

> >> microblazeel | atest-895b0183a89c15f5e2305... | http://autobuild.buildroot.net/results/b05ef59f1fd20800da2f407f64c369b9b5252328
> >> microblazeel | atest-895b0183a89c15f5e2305... | http://autobuild.buildroot.net/results/35b4a1e2a47f4e169e286fa8d25606821a88cc58  

Those ones are due to me having forgotten to rebuild the Microblaze
toolchain. I've just started the build, I will deploy once the build is
finished.

Thanks for reporting the issue!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

       reply	other threads:[~2017-05-04  7:30 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     ` Thomas Petazzoni [this message]
     [not found]       ` <035B547B-A554-4715-A235-95E6A1E14EE9@uclibc-ng.org>
2017-05-04  7:57         ` [Buildroot] [autobuild.buildroot.net] Your build results for 2017-05-02 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
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=20170504093049.27618dbf@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