From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 0/3] Add go language support
Date: Tue, 3 May 2016 09:08:57 +0200 [thread overview]
Message-ID: <20160503090857.23f362ea@free-electrons.com> (raw)
In-Reply-To: <1462207070.27026.20.camel@infradead.org>
Hello,
On Mon, 02 May 2016 09:37:50 -0700, Geoff Levand wrote:
> I have the patch below that adds BR2_TOOLCHAIN_HAS_THREADS. Is
> it enough to pull in the toolchain?
No, adding dependencies at the Config.in level doesn't change anything
in terms of build order.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-05-03 7:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 19:31 [Buildroot] [PATCH v3 0/3] Add go language support Geoff Levand
2016-04-04 19:31 ` [Buildroot] [PATCH v3 3/3] flannel: new package Geoff Levand
2016-04-20 21:03 ` Thomas Petazzoni
2016-04-04 19:31 ` [Buildroot] [PATCH v3 2/3] go: new host package Geoff Levand
2016-04-20 21:03 ` Thomas Petazzoni
2016-04-04 19:31 ` [Buildroot] [PATCH v3 1/3] go-bootstrap: " Geoff Levand
2016-04-20 21:02 ` Thomas Petazzoni
2016-04-22 1:09 ` Cam Hutchison
2016-04-22 9:51 ` Thomas Petazzoni
2016-04-22 21:41 ` Cam Hutchison
2016-04-22 21:49 ` Thomas Petazzoni
2016-04-23 8:34 ` Peter Korsgaard
2016-04-06 5:05 ` [Buildroot] [PATCH v3 0/3] Add go language support Christian Stewart
2016-04-06 16:23 ` Geoff Levand
2016-04-21 20:43 ` Thomas Petazzoni
2016-04-25 16:27 ` Geoff Levand
2016-04-29 21:26 ` Geoff Levand
2016-04-30 12:03 ` Thomas Petazzoni
2016-05-01 3:43 ` Christian Stewart
2016-05-02 16:37 ` Geoff Levand
2016-05-03 7:08 ` Thomas Petazzoni [this message]
2016-05-06 19:57 ` Geoff Levand
2016-05-06 19:58 ` Geoff Levand
2016-05-07 23:48 ` Arnout Vandecappelle
2016-05-02 16:21 ` Geoff Levand
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=20160503090857.23f362ea@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