Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>,
	OE-core <openembedded-core@lists.openembedded.org>
Cc: Marek Vasut <marex@denx.de>, Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: State of Sumo
Date: Sat, 21 Apr 2018 00:07:35 +0200	[thread overview]
Message-ID: <9b3314e3-2749-ce60-eede-a9cccec4e6ed@gmail.com> (raw)
In-Reply-To: <CAJTo0LYPdtHXqbKR5nm_EVzQ07Pju476n3Tahxp_zf=STW=LRw@mail.gmail.com>

On 04/20/2018 11:57 PM, Burton, Ross wrote:
> Hi,
> 
> We'll hopefully be firing the 2.5 RC build on Monday, so I did a build
> today to see where we stand. As is typical we got two new failures on
> the autobuilder...  My test build included the pseudo bump which
> caused an almost complete rebuild, which is a great way to shake out
> intermittent failures.
> 
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=12704
> Go appears to be using the target CFLAGS when using the host compiler,
> with predictable failures when the host is old and doesn't support new
> flags.
> 
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=12705
> u-boot build failure

Is there any chance you can tar-up the whole U-Boot build dir and make
it available, so it could be debugged ?

-- 
Best regards,
Marek Vasut


  reply	other threads:[~2018-04-20 22:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-20 21:57 State of Sumo Burton, Ross
2018-04-20 22:07 ` Marek Vasut [this message]
2018-04-20 22:09 ` Andre McCurdy
2018-04-21  8:08   ` Burton, Ross
2018-04-21  8:09     ` Burton, Ross
2018-04-21 10:02       ` Burton, Ross
2018-04-21 13:15         ` Matt Madison
2018-04-21 18:09   ` Khem Raj
2018-04-20 22:42 ` Peter Kjellerstedt
2018-04-21  8:08   ` Burton, Ross
2018-04-23 10:18     ` Peter Kjellerstedt

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=9b3314e3-2749-ce60-eede-a9cccec4e6ed@gmail.com \
    --to=marek.vasut@gmail.com \
    --cc=marex@denx.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    --cc=ross.burton@intel.com \
    /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