Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Kristian Amlie <kristian.amlie@mender.io>
To: Khem Raj <raj.khem@gmail.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH V7] go: Add recipes for golang compilers and tools
Date: Mon, 13 Mar 2017 14:36:28 +0100	[thread overview]
Message-ID: <797c9cb6-a50b-968d-005e-ecccfbf57791@mender.io> (raw)
In-Reply-To: <CAMKF1sq5DUzTfUBTovp5RyjmWyzcCRJbitRf1sZCO3mZgRNC5w@mail.gmail.com>

On 09/03/17 08:27, Khem Raj wrote:
> On Wed, Mar 8, 2017 at 11:03 PM, Kristian Amlie
> <kristian.amlie@mender.io> wrote:
>> On 08/03/17 23:19, Khem Raj wrote:
>>>> ...
>>>> For the following go-1.4 recipes:
>>>>
>>>> I wouldn't recommend fixing go-native at version 1.4, which is now
>>>> postiviely ancient.
>>>> Instead, add go1.4.3's SRC_URI into the go-native recipe, loading it
>>>> in the right place so
>>>> that make.bash finds it.  This way, you can have all the go toolchain
>>>> recipes build at the
>>>> same version.  The go team only supports go1.4 for bootstrapping the
>>>> compiler build now
>>>> anyway, IIRC.
>>>
>>> since we do not use go-native for anything other than bootstrapping
>>> right now, thats why it is there. there is no intent of providing a
>>> go-native version for general consumption
>>
>> Just FYI, in Mender we use the latest go-native, provided by
>> github.com/mem/oe-meta-go, to compile some build tools. The layer has a
>> separate go-bootstrap recipe, which is locked to 1.4, for the purpose of
>> creating go-native and go-cross.
> 
> Thanks for info. we should add it here as well.

What work is going on in this regard right now? We will need this fixed
rather soon, since currently it conflicts with the existing, external layer.

I could take a look at this myself, but I'm no Go toolchain expert, more
on the consumption side, so my solution may not be the optimal one.

-- 
Kristian


  reply	other threads:[~2017-03-13 13:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-03 23:18 [PATCH V7] go: Add recipes for golang compilers and tools Khem Raj
2017-03-06 15:05 ` Leonardo Sandoval
2017-03-06 18:47   ` Khem Raj
2017-03-06 20:00 ` Matt Madison
2017-03-08 22:19   ` Khem Raj
2017-03-09  7:03     ` Kristian Amlie
2017-03-09  7:27       ` Khem Raj
2017-03-13 13:36         ` Kristian Amlie [this message]
2017-03-09 13:19       ` Matt Madison
2017-03-09 13:17     ` Matt Madison
  -- strict thread matches above, loose matches on Subject: below --
2017-03-06 18:46 Khem Raj
2017-03-06 20:51 ` Burton, Ross
2017-03-06 20:56   ` Khem Raj

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=797c9cb6-a50b-968d-005e-ecccfbf57791@mender.io \
    --to=kristian.amlie@mender.io \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.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