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] Analysis of build results for 2017-10-30
Date: Wed, 1 Nov 2017 10:45:32 +0100	[thread overview]
Message-ID: <20171101104532.43dcd164@windsurf> (raw)
In-Reply-To: <CANQCQpYxR6nParzHgEswkZyh8K2-DUHnTu5VsOtyJOksd3rU5w@mail.gmail.com>

Hello,

On Tue, 31 Oct 2017 21:37:28 -0500, Matthew Weber wrote:

> > This is happening only on ARC. Why? Matt Weber proposed a patch,
> > https://patchwork.ozlabs.org/patch/832397/, but I am not terribly
> > convinced because it doesn't explain why this problem happens only on
> > ARC, and why it appeared suddenly.  
> 
> I kicked off a test build reverting the following commit.  We'll see
> in the morning if it changed the behavior or the pass/fail.  (ie bump
> from GCC 6.x to 7.x)
> 5bd21f991f3 Evgeniy Didin     2017-09-21 21:28:28

OK, we'll see the result.

> One interesting thing to notes is the test-pkg is using a external ARC
> GCC6 uclibc toolchain  and the failing builds are all internal
> toolchain and GCC 7.

Yes. But we have other toolchains tested by test-pkg that use gcc 7.x,
so I'm surprised the problem doesn't pop up on other architectures.


> >>          arc |       host-uboot-tools-2017.07 | NOK | http://autobuild.buildroot.net/results/9567703c95823be10400c0a330c3997a4cd6a62c | ORPH
> >>          arm |       host-uboot-tools-2017.07 | NOK | http://autobuild.buildroot.net/results/e3ee47e30a01e68a80fcbef3178f8eb051fe509f | ORPH
> >>          sh4 |       host-uboot-tools-2017.07 | NOK | http://autobuild.buildroot.net/results/7d60ebf31fd9df7a5fef7e7723859c32d7972f5b | ORPH  
> >
> > The libfdt/python issue. Matt Weber has proposed a patch to fix it:
> > https://patchwork.ozlabs.org/patch/827287/, however I have some
> > questions/concerns about it.  
> 
> Should we just wait for the November uboot release that resolves the
> underlying design issue upstream?

No, because we want to fix this problem before the next Buildroot
release in November.

Unrelated note: when you're replying to only a few parts of a lengthy
e-mail, it's good practice to delete the parts of the e-mail that are
not relevant. See what I did here :)

Thanks!

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

  reply	other threads:[~2017-11-01  9:45 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-31  7:00 [Buildroot] [autobuild.buildroot.net] Build results for 2017-10-30 Thomas Petazzoni
2017-10-31 22:05 ` [Buildroot] Analysis of build " Thomas Petazzoni
2017-11-01  2:37   ` Matthew Weber
2017-11-01  9:45     ` Thomas Petazzoni [this message]
2017-11-01 10:01       ` Alexey Brodkin
2017-11-01 10:24         ` Thomas Petazzoni
2017-11-01 10:31           ` Alexey Brodkin
2017-11-02  2:31           ` Waldemar Brodkorb
2017-11-02  8:06             ` Thomas Petazzoni
2017-11-01 13:24       ` Matthew Weber
2017-11-01 13:37         ` Thomas Petazzoni
2017-11-01 10:17   ` Samuel Martin
2017-11-01 13:40     ` Thomas Petazzoni
2017-11-01 18:03   ` Baruch Siach
2017-11-02 10:54     ` Peter Korsgaard
2017-11-03 22:31       ` Peter Korsgaard
2017-11-02 10:46   ` Peter Korsgaard
2017-11-02 17:43   ` Yann E. MORIN
2017-11-02 18:08     ` Yann E. MORIN
2017-11-02 20:04     ` Thomas Petazzoni
2017-11-02 20:55       ` Yann E. MORIN
2017-11-02 22:21   ` Thomas Petazzoni
2017-11-02 22:30     ` Alexey Brodkin
2017-11-03 11:17     ` Angelo Compagnucci
2017-11-03 13:38       ` Thomas Petazzoni
2017-11-03 13:46         ` Angelo Compagnucci
2017-11-03 13:52           ` Thomas Petazzoni
2017-11-03 14:18             ` Angelo Compagnucci
2017-11-03 14:28               ` Thomas Petazzoni
2017-11-03 14:35                 ` Angelo Compagnucci
2017-11-03 14:41                   ` Thomas Petazzoni
2017-11-04 22:18     ` Arnout Vandecappelle
2017-11-04 22:20       ` Thomas Petazzoni
2017-11-04 22:36         ` Peter Korsgaard
2017-11-05 14:40           ` Thomas Petazzoni
2017-11-05 19:36             ` Peter Korsgaard
2017-11-05 22:35               ` Thomas Petazzoni
2017-11-09 20:58       ` Alexey Brodkin
2017-11-02 22:22   ` Alexey Brodkin
2017-11-08 12:49   ` Johan Oudinet
2017-11-08 16:16     ` Matthew Weber
2017-11-08 17:33       ` Yann E. MORIN
2017-11-08 19:35         ` Matthew Weber

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=20171101104532.43dcd164@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