Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>,
	Matt Madison <matt@madison.systems>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2 0/8] go1.10 update and misc improvements
Date: Wed, 28 Feb 2018 10:47:41 +0000	[thread overview]
Message-ID: <1519814861.3436.1.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAP9ODKpB38Kpfj3EUdGNM+dL_A0VM03mP0isV4Vg_0DZ8Jw14w@mail.gmail.com>

On Tue, 2018-02-27 at 14:16 -0300, Otavio Salvador wrote:
> On Tue, Feb 27, 2018 at 9:36 AM, Matt Madison <matt@madison.systems>
> wrote:
> > 
> > New in v2:
> >     * Fixed Upstream-Status line in go patches
> >     * Added GOTMPDIR to do_configure[dirs]
> > 
> > Updates to the go recipes and bbclasses for go1.10, which
> > moves the bulk of the toolchain bootstrap and build out
> > of the 'make.bash' script and to the 'dist' tool.  This
> > required a rework of the patches.
> > 
> > go1.10 introduces significant changes to the go build
> > tool as well, requiring some further patches to make
> > it work for OE builds.
> > 
> > See https://golang.org/doc/go1.10 for a complete list
> > of new features and changes.
> > 
> > Following the update are some cleanup/improvement
> > patches.
> I tested those patches and they are working fine. I pinged Matt
> specifically about one patch that seems that could be simplified. So
> please wait until we get back on this before merging it.
> 
> If possible to put this on MUT so we see if any issue is raised up,
> it'd be good as well :-)

I tested it in -next, one issue:

FAIL: test_go_dep_build (gotoolchain.oeGoToolchainSelfTest)

from https://autobuilder.yocto.io/builders/nightly-oe-selftest/builds/8
57/steps/Running%20oe-selftest/logs/stdio

(can reproduce with oe-selftest -r
gotoolchain.oeGoToolchainSelfTest.test_go_dep_build)

Cheers,

Richard


  reply	other threads:[~2018-02-28 10:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-27 12:36 [PATCH v2 0/8] go1.10 update and misc improvements Matt Madison
2018-02-27 12:36 ` [PATCH v2 1/8] go: update go 1.9 -> go 1.10 Matt Madison
2018-02-28 11:00   ` Burton, Ross
2018-02-28 19:48   ` Khem Raj
2018-02-28 20:33     ` Matt Madison
2018-02-28 20:41       ` Khem Raj
2018-02-27 12:36 ` [PATCH v2 2/8] go: set GOMIPS envrionment variable Matt Madison
2018-02-27 12:36 ` [PATCH v2 3/8] go.bbclass: rename GO_TMPDIR -> GOTMPDIR Matt Madison
2018-02-27 12:36 ` [PATCH v2 4/8] go.bbclass: remove debug-related commands Matt Madison
2018-02-27 12:36 ` [PATCH v2 5/8] go.bbclass: don't stage test data with sources Matt Madison
2018-02-27 12:36 ` [PATCH v2 6/8] go.bbclass: ptest cleanup and improvements Matt Madison
2018-02-27 12:36 ` [PATCH v2 7/8] goarch.bbclass: disable shared runtime for nativesdk builds Matt Madison
2018-02-27 12:36 ` [PATCH v2 8/8] go: move common settings to go-common.inc Matt Madison
2018-02-27 17:16 ` [PATCH v2 0/8] go1.10 update and misc improvements Otavio Salvador
2018-02-28 10:47   ` Richard Purdie [this message]
2018-02-28 11:37     ` Richard Purdie
2018-02-28 11:42       ` Otavio Salvador
2018-02-28 11:44         ` Richard Purdie
2018-02-28 12:07           ` Matt Madison

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=1519814861.3436.1.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=matt@madison.systems \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio.salvador@ossystems.com.br \
    /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