Yes, just marked it. Thanks for the reminder.
Ross
On 22 November 2017 at 20:58, Matt Madison wrote:
> On Fri, Nov 17, 2017 at 8:02 AM, Burton, Ross
> wrote:
> > I had a hunch that was the problem this morning after looking again at
> the
> > patch set. Thanks for confirming.
>
> Ross,
>
> C
On Fri, Nov 17, 2017 at 8:02 AM, Burton, Ross wrote:
> I had a hunch that was the problem this morning after looking again at the
> patch set. Thanks for confirming.
Ross,
Can the BUILD_CC patch go back into your queue again?
Thanks,
-Matt
>
> Ross
>
> On 17 November 2017 at 15:49, Matt Madis
On Fri, Nov 17, 2017 at 7:49 AM, Matt Madison wrote:
> On Thu, Nov 16, 2017 at 3:29 PM, Matt Madison wrote:
>> On Thu, Nov 16, 2017 at 12:29 PM, Burton, Ross wrote:
>>> Looks like this is failing on some of our autobuilders, such as
>>> https://autobuilder.yocto.io/builders/nightly-musl-x86-64/b
I had a hunch that was the problem this morning after looking again at the
patch set. Thanks for confirming.
Ross
On 17 November 2017 at 15:49, Matt Madison wrote:
> On Thu, Nov 16, 2017 at 3:29 PM, Matt Madison
> wrote:
> > On Thu, Nov 16, 2017 at 12:29 PM, Burton, Ross
> wrote:
> >> Looks
On Thu, Nov 16, 2017 at 3:29 PM, Matt Madison wrote:
> On Thu, Nov 16, 2017 at 12:29 PM, Burton, Ross wrote:
>> Looks like this is failing on some of our autobuilders, such as
>> https://autobuilder.yocto.io/builders/nightly-musl-x86-64/builds/58/steps/BuildImages/logs/stdio
>
> I'm looking into
On Thu, Nov 16, 2017 at 12:29 PM, Burton, Ross wrote:
> Looks like this is failing on some of our autobuilders, such as
> https://autobuilder.yocto.io/builders/nightly-musl-x86-64/builds/58/steps/BuildImages/logs/stdio
I'm looking into it.
Thanks,
-Matt
>
> | cmd/go/internal/vet
> | # cmd/api
>
Looks like this is failing on some of our autobuilders, such as
https://autobuilder.yocto.io/builders/nightly-musl-x86-64/builds/58/steps/BuildImages/logs/stdio
| cmd/go/internal/vet
| # cmd/api
|
/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-musl-x86-64/build/build/tmp/work/core2-64-poky
Yes, drat it, v3 should fix that.
Thanks,
-Matt
On Tue, Nov 14, 2017 at 9:20 AM, Otavio Salvador
wrote:
> Hello Matt,
>
> A minor thing:
>
> Upstream-Status: Pending
>
> On Tue, Nov 14, 2017 at 3:18 PM, Matt Madison wrote:
>> For cross-canadian builds, we were accidentally using
>> the crosssdk
Hello Matt,
A minor thing:
Upstream-Status: Pending
On Tue, Nov 14, 2017 at 3:18 PM, Matt Madison wrote:
> For cross-canadian builds, we were accidentally using
> the crosssdk C compiler when building the Go compiler
> bootstrap. Add a patch to the make script to let us
> use BUILD_CC, and pre
For cross-canadian builds, we were accidentally using
the crosssdk C compiler when building the Go compiler
bootstrap. Add a patch to the make script to let us
use BUILD_CC, and prepend do_compile to set it in
the local environment to ensure that the trailing
blank gets stripped, since that confus
10 matches
Mail list logo
