Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vlad Zakharov <Vladislav.Zakharov@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [arc-buildroot] Analysis of build results for 2017-02-13
Date: Wed, 22 Feb 2017 13:01:13 +0000	[thread overview]
Message-ID: <1487768472.25108.68.camel@synopsys.com> (raw)
In-Reply-To: <20170222134828.17a6bcb0@free-electrons.com>

Hi Thomas,

On Wed, 2017-02-22 at 13:48 +0100, Thomas Petazzoni wrote:
> Hello,
> 
> On Wed, 22 Feb 2017 11:26:00 +0000, Vlad Zakharov wrote:
> > 
> > We are looking at the issue. I hope it will be solved rather wool but unfortunately I am sure fix will be ready
> > before
> > BR release.
> 
> I guess you meant "not sure" ?

You are right, it was a typo, I'm sorry.

> 
> > 
> > So I can turn off this package now and then provide fix and turn the
> > package on again. What do you think about it?
> 
> That's OK for me. Can you send a patch doing so?

Sure, I will send it soon.

> 
> We also recently disabled the "trousers" package on ARC, also for a
> toolchain reason.
> 
> Will you remember all the packages that we disabled due to an ARC
> toolchain issue? Should we mark them with a special comment, so that
> you can grep for it, like:
> 
> 	# ARC toolchain issue
> 	depends on !BR2_arc

We are trying to keep the list of packages disabled due to ARC toolchain failures.?
Nevertheless it sounds like a good idea - we won't miss anything.

> 
> Thomas
-- 
Best regards,
Vlad Zakharov <vzakhar@synopsys.com>

      reply	other threads:[~2017-02-22 13:01 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-14  7:28 [Buildroot] [autobuild.buildroot.net] Build results for 2017-02-13 Thomas Petazzoni
2017-02-14 13:27 ` [Buildroot] Analysis of build " Thomas Petazzoni
2017-02-14 14:51   ` Peter Korsgaard
2017-02-14 15:10     ` Thomas Petazzoni
2017-02-14 19:21       ` Peter Korsgaard
2017-02-14 20:03         ` Thomas Petazzoni
2017-02-14 20:21           ` Peter Korsgaard
2017-02-14 15:44   ` Philippe Proulx
2017-02-14 16:39   ` Yann E. MORIN
2017-02-14 20:02     ` Thomas Petazzoni
2017-02-14 20:05       ` Yann E. MORIN
2017-02-14 18:02   ` Baruch Siach
2017-02-14 19:37     ` Peter Korsgaard
2017-02-14 22:29   ` Thomas Petazzoni
2017-02-15  7:38     ` Peter Korsgaard
2017-02-15  8:33       ` Thomas Petazzoni
2017-02-15 23:14         ` Arnout Vandecappelle
2017-02-16  8:36           ` Thomas Petazzoni
2017-02-15  2:45   ` Sam Bobroff
2017-02-15  8:37     ` Thomas Petazzoni
2017-02-15 13:22   ` Gustavo Zacarias
2017-02-16 20:34   ` Bernd Kuhls
2017-02-22 11:26   ` [Buildroot] [arc-buildroot] " Vlad Zakharov
2017-02-22 12:48     ` Thomas Petazzoni
2017-02-22 13:01       ` Vlad Zakharov [this message]

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=1487768472.25108.68.camel@synopsys.com \
    --to=vladislav.zakharov@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