From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC v2 1/4] package/go: fixing crosscompilation settings
Date: Wed, 25 Oct 2017 09:41:20 +0200 [thread overview]
Message-ID: <87a80f65en.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20171021215107.1e4fa5e2@windsurf> (Thomas Petazzoni's message of "Sat, 21 Oct 2017 21:51:07 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
> Hello,
> On Mon, 16 Oct 2017 19:08:45 +0200, Angelo Compagnucci wrote:
>> This patch fixes a bug with the BR2_TOOLCHAIN_HAS_THREADS variable
>> handling which causes CGO_ENABLED to be always 0.
>>
>> Furthermore, it fixes the cross compilation options for the go compiler:
>> setting CGO_ENABLED should be done only for the target compiler not the
>> host one.
>>
>> Signed-off-by: Angelo Compagnucci <angelo.compagnucci@gmail.com>
>> ---
>> package/go/go.mk | 14 ++++++++------
>> 1 file changed, 8 insertions(+), 6 deletions(-)
> Thanks applied the patch, with Christian's Acked-by.
Committed to 2017.02.x, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2017-10-25 7:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 17:08 [Buildroot] [RFC v2 1/4] package/go: fixing crosscompilation settings Angelo Compagnucci
2017-10-16 17:08 ` [Buildroot] [RFC v2 2/4] package/pkg-golang: new package infrastructure Angelo Compagnucci
2017-10-21 19:55 ` Thomas Petazzoni
2017-10-23 16:36 ` Angelo Compagnucci
2017-10-16 17:08 ` [Buildroot] [RFC v2 3/4] docs/manual: adding documentation for the golang infrastructure Angelo Compagnucci
2017-10-16 17:08 ` [Buildroot] [RFC v2 4/4] package/flannel: converting to " Angelo Compagnucci
2017-10-21 19:51 ` [Buildroot] [RFC v2 1/4] package/go: fixing crosscompilation settings Thomas Petazzoni
2017-10-22 22:48 ` Peter Korsgaard
2017-10-25 7:41 ` Peter Korsgaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-10-19 17:20 [Buildroot] [RFC, v2, " Christian Stewart
2017-10-19 19:54 ` Thomas Petazzoni
2017-10-19 20:17 ` Christian Stewart
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=87a80f65en.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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