From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv6] package/golang: new package
Date: Wed, 4 Nov 2015 18:31:19 +0100 [thread overview]
Message-ID: <20151104183119.107ccc45@free-electrons.com> (raw)
In-Reply-To: <20151104172118.GB4072@free.fr>
Hello,
On Wed, 4 Nov 2015 18:21:18 +0100, Yann E. MORIN wrote:
> On 2015-11-04 15:39 +0000, Christian Stewart spake thusly:
> > Is there anything that needs to be done regarding golang for it to be
> > merged? After golang we can push towards docker support.
>
> IIRC, we need to provide an $(TUPLE)-go to act as a cross-compiler. That
> would be a shell script that exports the appropriate environement
> variables (you provided the list) and then calls the real go executable.
>
> Otherwise, just calling the go program, even when set up as a
> cross-compiler, does not produce target binaries as we've observed.
Correct. Also, I think I raised a few comments (about gofmt, about the
situations where go in the target is useful). Those comments were
answered, but it would be nicer if the answers were turned into actual
comments into the code, or in the Config.in help text.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-11-04 17:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 17:24 [Buildroot] [PATCHv6] package/golang: new package Yann E. MORIN
2015-07-31 6:33 ` Jerzy Grzegorek
2015-10-21 21:07 ` Thomas Petazzoni
[not found] ` <CA+h8R2p5xgF7rJJW5z0AzB7b359F=S9yWrXpiTmCVK-D0Sk8pw@mail.gmail.com>
[not found] ` <20151021232135.1997edb6@free-electrons.com>
2015-10-21 21:37 ` Christian Stewart
2015-10-21 21:37 ` [Buildroot] Fwd: " Christian Stewart
2015-11-04 15:39 ` [Buildroot] " Christian Stewart
2015-11-04 17:21 ` Yann E. MORIN
2015-11-04 17:31 ` Thomas Petazzoni [this message]
2015-11-04 21:21 ` Christian Stewart
2015-11-05 21:15 ` Yann E. MORIN
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=20151104183119.107ccc45@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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