From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2.1 1/6] package/go: Build host tools with host CC
Date: Wed, 25 May 2016 16:05:29 +0200 [thread overview]
Message-ID: <20160525160529.2c19eea9@free-electrons.com> (raw)
In-Reply-To: <1464125645.5014.52.camel@infradead.org>
Hello,
On Tue, 24 May 2016 14:34:05 -0700, Geoff Levand wrote:
> +ifneq ($(ARCH),$(HOSTARCH))
> define HOST_GO_BUILD_CMDS
> - cd $(@D)/src && $(HOST_GO_MAKE_ENV) ./make.bash
> + cd $(@D)/src && $(HOST_GO_MAKE_ENV) $(HOST_GO_TARGET_CC) ./make.bash
> + mkdir -p $(HOST_GO_TMP)
> + mv $(@D)/pkg/tool $(HOST_GO_TMP)/
> + mv $(@D)/bin/ $(HOST_GO_TMP)/
> endef
> +else
> +define HOST_GO_BUILD_CMDS
> + cd $(@D)/src && $(HOST_GO_MAKE_ENV) $(HOST_GO_HOST_CC) ./make.bash
> + mkdir -p $(HOST_GO_TMP)
> + mv $(@D)/pkg/tool $(HOST_GO_TMP)/
> + mv $(@D)/bin/ $(HOST_GO_TMP)/
> + cd $(@D)/src && $(HOST_GO_MAKE_ENV) $(HOST_GO_TARGET_CC) ./make.bash
Just to make sure I understand correctly: you build everything with
HOST_GO_HOST_CC first, and put the files generated in pkg/tool and bin/
on the side in HOST_GO_TMP, and then rebuild everything again with
HOST_GO_TARGET_CC. Then later on, the installation step will pick up
bin/ and pkg/tool from HOST_GO_TMP, and the rest from $(@D) directly ?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-05-25 14:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 22:25 [Buildroot] [PATCH v2 0/6] Fixes for go language support Geoff Levand
2016-05-19 22:25 ` [Buildroot] [PATCH v2 1/6] package/go: Build host tools with host CC Geoff Levand
2016-05-24 19:11 ` Thomas Petazzoni
2016-05-24 21:31 ` Geoff Levand
2016-05-24 21:34 ` [Buildroot] [PATCH v2.1 " Geoff Levand
2016-05-25 14:05 ` Thomas Petazzoni [this message]
2016-05-25 16:41 ` Geoff Levand
2016-05-25 20:59 ` Thomas Petazzoni
2016-05-26 17:24 ` Geoff Levand
2016-05-26 17:30 ` Thomas Petazzoni
2016-05-19 22:25 ` [Buildroot] [PATCH v2 4/6] package/go: Add HOST_GO_CGO_ENABLED Geoff Levand
2016-05-19 22:25 ` [Buildroot] [PATCH v2 6/6] package/go: Set file timestamp Geoff Levand
2016-05-24 19:13 ` Thomas Petazzoni
2016-05-24 20:12 ` Christian Stewart
2016-05-24 21:35 ` Geoff Levand
2016-05-19 22:25 ` [Buildroot] [PATCH v2 3/6] package/flannel: Use HOST_GO_TARGET_ENV Geoff Levand
2016-05-19 22:25 ` [Buildroot] [PATCH v2 5/6] package/flannel: Add BR2_TOOLCHAIN_HAS_THREADS Geoff Levand
2016-05-19 22:25 ` [Buildroot] [PATCH v2 2/6] package/go: Add HOST_GO_TARGET_ENV 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=20160525160529.2c19eea9@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