NetCube-Systems-Austria/kumquat-buildroot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
7a5873ce5a
kumquat-buildroot/package/go/go.mk

151 lines
4.2 KiB
Makefile
Raw Normal View History

go: new host package Add a new package 'go' which builds the host cross compiler and libraries for the go programming language. Signed-off-by: Geoff Levand <geoff@infradead.org> [Thomas: - Put the computation of GO_GOARM inside the ifeq ($(BR2_arm),y) condition rather than duplicating this condition. - Remove the GO_GOARCH=unknown case, since there is no way to fall in this case as only supported architectures can use host-go. - Remove the GO_GOARM=unknown case, since we are sure that only ARMv5/6/7 will use host-go. - Rename HOST_GO_FINAL to HOST_GO_ROOT, since it's really the "root" of the Go installation. - Remove visible Config.in.host option.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-04-04 21:31:49 +02:00
################################################################################
#
# go
#
################################################################################
package/go: security bump to 1.15.5 Fixes the following security issues: - math/big: panic during recursive division of very large numbers A number of math/big.Int methods (Div, Exp, DivMod, Quo, Rem, QuoRem, Mod, ModInverse, ModSqrt, Jacobi, and GCD) can panic when provided crafted large inputs. For the panic to happen, the divisor or modulo argument must be larger than 3168 bits (on 32-bit architectures) or 6336 bits (on 64-bit architectures). Multiple math/big.Rat methods are similarly affected. crypto/rsa.VerifyPSS, crypto/rsa.VerifyPKCS1v15, and crypto/dsa.Verify may panic when provided crafted public keys and signatures. crypto/ecdsa and crypto/elliptic operations may only be affected if custom CurveParams with unusually large field sizes (several times larger than the largest supported curve, P-521) are in use. Using crypto/x509.Verify on a crafted X.509 certificate chain can lead to a panic, even if the certificates don’t chain to a trusted root. The chain can be delivered via a crypto/tls connection to a client, or to a server that accepts and verifies client certificates. net/http clients can be made to crash by an HTTPS server, while net/http servers that accept client certificates will recover the panic and are unaffected. Moreover, an application might crash invoking crypto/x509.(*CertificateRequest).CheckSignature on an X.509 certificate request or during a golang.org/x/crypto/otr conversation. Parsing a golang.org/x/crypto/openpgp Entity or verifying a signature may crash. Finally, a golang.org/x/crypto/ssh client can panic due to a malformed host key, while a server could panic if either PublicKeyCallback accepts a malformed public key, or if IsUserAuthority accepts a certificate with a malformed public key. Thanks to the Go Ethereum team and the OSS-Fuzz project for reporting this. Thanks to Rémy Oudompheng and Robert Griesemer for their help developing and validating the fix. This issue is CVE-2020-28362 and Go issue golang.org/issue/42552. - cmd/go: arbitrary code execution at build time through cgo The go command may execute arbitrary code at build time when cgo is in use. This may occur when running go get on a malicious package, or any other command that builds untrusted code. This can be caused by malicious gcc flags specified via a #cgo directive, or by a malicious symbol name in a linked object file. Thanks to Imre Rad and to Chris Brown and Tempus Ex respectively for reporting these issues. These issues are CVE-2020-28367 and CVE-2020-28366, and Go issues golang.org/issue/42556 and golang.org/issue/42559 respectively. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2020-11-13 11:31:11 +01:00
GO_VERSION = 1.15.5
go: new host package Add a new package 'go' which builds the host cross compiler and libraries for the go programming language. Signed-off-by: Geoff Levand <geoff@infradead.org> [Thomas: - Put the computation of GO_GOARM inside the ifeq ($(BR2_arm),y) condition rather than duplicating this condition. - Remove the GO_GOARCH=unknown case, since there is no way to fall in this case as only supported architectures can use host-go. - Remove the GO_GOARM=unknown case, since we are sure that only ARMv5/6/7 will use host-go. - Rename HOST_GO_FINAL to HOST_GO_ROOT, since it's really the "root" of the Go installation. - Remove visible Config.in.host option.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-04-04 21:31:49 +02:00
GO_SITE = https://storage.googleapis.com/golang
GO_SOURCE = go$(GO_VERSION).src.tar.gz
boot, package: use SPDX short identifier for BSD-3c We want to use SPDX identifier for license string as much as possible. SPDX short identifier for BSD-3c is BSD-3-Clause. This change is done using following command. find . -name "*.mk" | xargs sed -ri '/LICENSE( )?[\+:]?=/s/BSD-3c/BSD-3-Clause/g' Signed-off-by: Rahul Bedarkar <rahulbedarkar89@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-03-30 15:43:38 +02:00
GO_LICENSE = BSD-3-Clause
go: new host package Add a new package 'go' which builds the host cross compiler and libraries for the go programming language. Signed-off-by: Geoff Levand <geoff@infradead.org> [Thomas: - Put the computation of GO_GOARM inside the ifeq ($(BR2_arm),y) condition rather than duplicating this condition. - Remove the GO_GOARCH=unknown case, since there is no way to fall in this case as only supported architectures can use host-go. - Remove the GO_GOARM=unknown case, since we are sure that only ARMv5/6/7 will use host-go. - Rename HOST_GO_FINAL to HOST_GO_ROOT, since it's really the "root" of the Go installation. - Remove visible Config.in.host option.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-04-04 21:31:49 +02:00
GO_LICENSE_FILES = LICENSE
package/go: fix building host go toolchain when target isn't supported The go toolchain can cross-compile by default. So most of the time, building a toolchain that supports a target, allows us to also build go binaries for the host. This is how support for host go packages was added: we use the same toolchain that was initially built only for target. But we might want to build a go binary for the host, when compiling a target for which go isn't supported. Then, building host-go will fail: by default, we build go for a specific target, and give the toolchain bootstrap scripts the cross compiler we'll use. This change modifies this behaviour: we only assume the go toolchain is cross-capable if we know the current target is supported. Otherwise this is a simple host go tool. We don't need to set any of the options needed for cross-compilation in that case. Thus, only set all the target-specific go options under a condition that the target arch is supported. The only option we still set is HOST_GO_CGO_ENABLED, and we always set it to enabled. It was also considered to create a separate package to build the go-for-host compiler which would be used for host-go-packages, but that would lead to a lot of duplication and is completely unnecessary. Fixes: http://autobuild.buildroot.net/results/98b9c7aaff2af4d19adfedac00b768d92530ce94 http://autobuild.buildroot.net/results/bed228995ce3778720f991df9b41345a7c724a46 http://autobuild.buildroot.net/results/3b3ea148165b96513ea511ee0d4adb334a6afac8 Signed-off-by: Anisse Astier <anisse@astier.eu> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Reviewed-by: Anisse Astier <anisse@astier.eu> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-04-15 22:49:51 +02:00
HOST_GO_DEPENDENCIES = host-go-bootstrap
package/go: implement go modules integration The Go compiler needs to know the "import path" to the root of package source repositories. Previously, this was done by creating a fake _gopath in the build directory and symlinking the package source into that path. Go has deprecated the GOPATH mechanism in favor of a new approach - Modules - which specifies the root import path (and dependencies) in a "go.mod" file. This commit moves Buildroot to use the new go.mod approach, which requires: - Passing GO111MODULE=on when building host or target Go packages. - Passing GOPROXY=off and -mod=vendor to prevent the Go module system from downloading by itself sources from the Internet. We currently only support Go packages that have all their dependencies in their source tree in "vendor" directories. - Specifying a <pkg>_GOMOD variable, which is used both to create a minimal go.mod file in the package source tree if it exists, and to invoke the right build targets. Indeed, all elements in <pkg>_BUILD_TARGETS are now relative to <pkg>_GOMOD. Reference: https://github.com/golang/go/wiki/Modules Signed-off-by: Christian Stewart <christian@paral.in> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-08-29 11:28:37 +02:00
HOST_GO_GOPATH = $(HOST_DIR)/usr/share/go-path
package/go: fix building host go toolchain when target isn't supported The go toolchain can cross-compile by default. So most of the time, building a toolchain that supports a target, allows us to also build go binaries for the host. This is how support for host go packages was added: we use the same toolchain that was initially built only for target. But we might want to build a go binary for the host, when compiling a target for which go isn't supported. Then, building host-go will fail: by default, we build go for a specific target, and give the toolchain bootstrap scripts the cross compiler we'll use. This change modifies this behaviour: we only assume the go toolchain is cross-capable if we know the current target is supported. Otherwise this is a simple host go tool. We don't need to set any of the options needed for cross-compilation in that case. Thus, only set all the target-specific go options under a condition that the target arch is supported. The only option we still set is HOST_GO_CGO_ENABLED, and we always set it to enabled. It was also considered to create a separate package to build the go-for-host compiler which would be used for host-go-packages, but that would lead to a lot of duplication and is completely unnecessary. Fixes: http://autobuild.buildroot.net/results/98b9c7aaff2af4d19adfedac00b768d92530ce94 http://autobuild.buildroot.net/results/bed228995ce3778720f991df9b41345a7c724a46 http://autobuild.buildroot.net/results/3b3ea148165b96513ea511ee0d4adb334a6afac8 Signed-off-by: Anisse Astier <anisse@astier.eu> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Reviewed-by: Anisse Astier <anisse@astier.eu> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-04-15 22:49:51 +02:00
HOST_GO_HOST_CACHE = $(HOST_DIR)/usr/share/host-go-cache
HOST_GO_ROOT = $(HOST_DIR)/lib/go
HOST_GO_TARGET_CACHE = $(HOST_DIR)/usr/share/go-cache
package/go: re-integrate GO_COMMON_ENV into HOST_GO_COMMON_ENV There is no point in having some common Go env variables defined in pkg-golang.mk:GO_COMMON_ENV, and some in package/go/go.mk:HOST_GO_COMMON_ENV. Let's move all of them to package/go/go.mk:HOST_GO_COMMON_ENV. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-08-29 11:14:35 +02:00
# We pass an empty GOBIN, otherwise "go install: cannot install
# cross-compiled binaries when GOBIN is set"
package/go: introduce HOST_GO_COMMON_ENV A few variables are common between HOST_GO_TARGET_ENV and HOST_GO_HOST_ENV, so let's introduce a HOST_GO_COMMON_ENV variable for those few common ones (which will increase in follow-up commits). Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-08-29 11:04:25 +02:00
HOST_GO_COMMON_ENV = \
package/go: implement go modules integration The Go compiler needs to know the "import path" to the root of package source repositories. Previously, this was done by creating a fake _gopath in the build directory and symlinking the package source into that path. Go has deprecated the GOPATH mechanism in favor of a new approach - Modules - which specifies the root import path (and dependencies) in a "go.mod" file. This commit moves Buildroot to use the new go.mod approach, which requires: - Passing GO111MODULE=on when building host or target Go packages. - Passing GOPROXY=off and -mod=vendor to prevent the Go module system from downloading by itself sources from the Internet. We currently only support Go packages that have all their dependencies in their source tree in "vendor" directories. - Specifying a <pkg>_GOMOD variable, which is used both to create a minimal go.mod file in the package source tree if it exists, and to invoke the right build targets. Indeed, all elements in <pkg>_BUILD_TARGETS are now relative to <pkg>_GOMOD. Reference: https://github.com/golang/go/wiki/Modules Signed-off-by: Christian Stewart <christian@paral.in> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-08-29 11:28:37 +02:00
GO111MODULE=on \
GOFLAGS=-mod=vendor \
package/go: re-integrate GO_COMMON_ENV into HOST_GO_COMMON_ENV There is no point in having some common Go env variables defined in pkg-golang.mk:GO_COMMON_ENV, and some in package/go/go.mk:HOST_GO_COMMON_ENV. Let's move all of them to package/go/go.mk:HOST_GO_COMMON_ENV. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-08-29 11:14:35 +02:00
GOROOT="$(HOST_GO_ROOT)" \
package/go: implement go modules integration The Go compiler needs to know the "import path" to the root of package source repositories. Previously, this was done by creating a fake _gopath in the build directory and symlinking the package source into that path. Go has deprecated the GOPATH mechanism in favor of a new approach - Modules - which specifies the root import path (and dependencies) in a "go.mod" file. This commit moves Buildroot to use the new go.mod approach, which requires: - Passing GO111MODULE=on when building host or target Go packages. - Passing GOPROXY=off and -mod=vendor to prevent the Go module system from downloading by itself sources from the Internet. We currently only support Go packages that have all their dependencies in their source tree in "vendor" directories. - Specifying a <pkg>_GOMOD variable, which is used both to create a minimal go.mod file in the package source tree if it exists, and to invoke the right build targets. Indeed, all elements in <pkg>_BUILD_TARGETS are now relative to <pkg>_GOMOD. Reference: https://github.com/golang/go/wiki/Modules Signed-off-by: Christian Stewart <christian@paral.in> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-08-29 11:28:37 +02:00
GOPATH="$(HOST_GO_GOPATH)" \
GOPROXY=off \
package/go: re-integrate GO_COMMON_ENV into HOST_GO_COMMON_ENV There is no point in having some common Go env variables defined in pkg-golang.mk:GO_COMMON_ENV, and some in package/go/go.mk:HOST_GO_COMMON_ENV. Let's move all of them to package/go/go.mk:HOST_GO_COMMON_ENV. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-08-29 11:14:35 +02:00
PATH=$(BR_PATH) \
GOBIN= \
CGO_ENABLED=$(HOST_GO_CGO_ENABLED)
package/go: introduce HOST_GO_COMMON_ENV A few variables are common between HOST_GO_TARGET_ENV and HOST_GO_HOST_ENV, so let's introduce a HOST_GO_COMMON_ENV variable for those few common ones (which will increase in follow-up commits). Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-08-29 11:04:25 +02:00
package/go: fix building host go toolchain when target isn't supported The go toolchain can cross-compile by default. So most of the time, building a toolchain that supports a target, allows us to also build go binaries for the host. This is how support for host go packages was added: we use the same toolchain that was initially built only for target. But we might want to build a go binary for the host, when compiling a target for which go isn't supported. Then, building host-go will fail: by default, we build go for a specific target, and give the toolchain bootstrap scripts the cross compiler we'll use. This change modifies this behaviour: we only assume the go toolchain is cross-capable if we know the current target is supported. Otherwise this is a simple host go tool. We don't need to set any of the options needed for cross-compilation in that case. Thus, only set all the target-specific go options under a condition that the target arch is supported. The only option we still set is HOST_GO_CGO_ENABLED, and we always set it to enabled. It was also considered to create a separate package to build the go-for-host compiler which would be used for host-go-packages, but that would lead to a lot of duplication and is completely unnecessary. Fixes: http://autobuild.buildroot.net/results/98b9c7aaff2af4d19adfedac00b768d92530ce94 http://autobuild.buildroot.net/results/bed228995ce3778720f991df9b41345a7c724a46 http://autobuild.buildroot.net/results/3b3ea148165b96513ea511ee0d4adb334a6afac8 Signed-off-by: Anisse Astier <anisse@astier.eu> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Reviewed-by: Anisse Astier <anisse@astier.eu> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-04-15 22:49:51 +02:00
ifeq ($(BR2_PACKAGE_HOST_GO_TARGET_ARCH_SUPPORTS),y)
go: new host package Add a new package 'go' which builds the host cross compiler and libraries for the go programming language. Signed-off-by: Geoff Levand <geoff@infradead.org> [Thomas: - Put the computation of GO_GOARM inside the ifeq ($(BR2_arm),y) condition rather than duplicating this condition. - Remove the GO_GOARCH=unknown case, since there is no way to fall in this case as only supported architectures can use host-go. - Remove the GO_GOARM=unknown case, since we are sure that only ARMv5/6/7 will use host-go. - Rename HOST_GO_FINAL to HOST_GO_ROOT, since it's really the "root" of the Go installation. - Remove visible Config.in.host option.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-04-04 21:31:49 +02:00
ifeq ($(BR2_arm),y)
GO_GOARCH = arm
ifeq ($(BR2_ARM_CPU_ARMV5),y)
GO_GOARM = 5
else ifeq ($(BR2_ARM_CPU_ARMV6),y)
GO_GOARM = 6
else ifeq ($(BR2_ARM_CPU_ARMV7A),y)
GO_GOARM = 7
endif
else ifeq ($(BR2_aarch64),y)
GO_GOARCH = arm64
else ifeq ($(BR2_i386),y)
GO_GOARCH = 386
else ifeq ($(BR2_x86_64),y)
GO_GOARCH = amd64
package/go: Fix powerpc64 config typo Fix typo in config powerpc64 depends. Go language only supports 64 bit powerpc. Also add BR2_powerpc64le to depends list. Signed-off-by: Geoff Levand <geoff@infradead.org> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-05-12 02:08:47 +02:00
else ifeq ($(BR2_powerpc64),y)
go: new host package Add a new package 'go' which builds the host cross compiler and libraries for the go programming language. Signed-off-by: Geoff Levand <geoff@infradead.org> [Thomas: - Put the computation of GO_GOARM inside the ifeq ($(BR2_arm),y) condition rather than duplicating this condition. - Remove the GO_GOARCH=unknown case, since there is no way to fall in this case as only supported architectures can use host-go. - Remove the GO_GOARM=unknown case, since we are sure that only ARMv5/6/7 will use host-go. - Rename HOST_GO_FINAL to HOST_GO_ROOT, since it's really the "root" of the Go installation. - Remove visible Config.in.host option.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-04-04 21:31:49 +02:00
GO_GOARCH = ppc64
package/go: Fix powerpc64 config typo Fix typo in config powerpc64 depends. Go language only supports 64 bit powerpc. Also add BR2_powerpc64le to depends list. Signed-off-by: Geoff Levand <geoff@infradead.org> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-05-12 02:08:47 +02:00
else ifeq ($(BR2_powerpc64le),y)
GO_GOARCH = ppc64le
package/go: Enable MIPS support Enable go language support for mips64 and mips64el (mips64le), which were added in go-1.6.2. Signed-off-by: Geoff Levand <geoff@infradead.org> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-05-20 00:33:25 +02:00
else ifeq ($(BR2_mips64),y)
GO_GOARCH = mips64
else ifeq ($(BR2_mips64el),y)
GO_GOARCH = mips64le
package/go: fix GO_ARCH for s390x arch Fixes: - http://autobuild.buildroot.net/results/82c440825290804c2fd6a92d916c93d2934e0a95 - http://autobuild.buildroot.net/results/e8f8e232fb6bf6167f25c82026f4e2321cca9c26 - http://autobuild.buildroot.net/results/7d4137c439ade81ab7bf141ad6504a69746d6dbc Signed-off-by: Alexander Egorenkov <egorenar@linux.ibm.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2020-10-02 11:19:45 +02:00
else ifeq ($(BR2_s390x),y)
GO_GOARCH = s390x
go: new host package Add a new package 'go' which builds the host cross compiler and libraries for the go programming language. Signed-off-by: Geoff Levand <geoff@infradead.org> [Thomas: - Put the computation of GO_GOARM inside the ifeq ($(BR2_arm),y) condition rather than duplicating this condition. - Remove the GO_GOARCH=unknown case, since there is no way to fall in this case as only supported architectures can use host-go. - Remove the GO_GOARM=unknown case, since we are sure that only ARMv5/6/7 will use host-go. - Rename HOST_GO_FINAL to HOST_GO_ROOT, since it's really the "root" of the Go installation. - Remove visible Config.in.host option.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-04-04 21:31:49 +02:00
endif
package/go: Add HOST_GO_TARGET_ENV For the convenience of package makefiles define the new make variables HOST_GO_TOOLDIR and HOST_GO_TARGET_ENV. Signed-off-by: Geoff Levand <geoff@infradead.org> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-05-26 20:21:32 +02:00
# For the convienience of target packages.
HOST_GO_TOOLDIR = $(HOST_GO_ROOT)/pkg/tool/linux_$(GO_GOARCH)
HOST_GO_TARGET_ENV = \
package/go: introduce HOST_GO_COMMON_ENV A few variables are common between HOST_GO_TARGET_ENV and HOST_GO_HOST_ENV, so let's introduce a HOST_GO_COMMON_ENV variable for those few common ones (which will increase in follow-up commits). Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-08-29 11:04:25 +02:00
$(HOST_GO_COMMON_ENV) \
package/go: Add HOST_GO_TARGET_ENV For the convenience of package makefiles define the new make variables HOST_GO_TOOLDIR and HOST_GO_TARGET_ENV. Signed-off-by: Geoff Levand <geoff@infradead.org> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-05-26 20:21:32 +02:00
GOARCH=$(GO_GOARCH) \
package/go: set GOCACHE to a host path Set the GOCACHE environment variable properly. It was previously unset, and defaults to $HOME/.cache/go-build. Signed-off-by: Christian Stewart <christian@paral.in> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-03-12 06:41:14 +01:00
GOCACHE="$(HOST_GO_TARGET_CACHE)" \
package/go: add double quotes around TARGET_CC/TARGET_CXX Using double quotes around TARGET_CC/TARGET_CXX is mandatory, since they are composed of several words when ccache support is enabled. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-05-26 21:06:26 +02:00
CC="$(TARGET_CC)" \
CXX="$(TARGET_CXX)" \
package/go: pass CFLAGS/CXXFLAGS/LDFLAGS in HOST_GO_TARGET_ENV HOST_GO_HOST_ENV is explicitly specifying HOST_CGO_{CFLAGS,CXXFLAGS,LDFLAGS}, so let's do the same for target packages. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-08-29 11:13:07 +02:00
CGO_CFLAGS="$(TARGET_CFLAGS)" \
CGO_CXXFLAGS="$(TARGET_CXXFLAGS)" \
CGO_LDFLAGS="$(TARGET_LDFLAGS)" \
package/go: Add HOST_GO_TARGET_ENV For the convenience of package makefiles define the new make variables HOST_GO_TOOLDIR and HOST_GO_TARGET_ENV. Signed-off-by: Geoff Levand <geoff@infradead.org> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-05-26 20:21:32 +02:00
GOTOOLDIR="$(HOST_GO_TOOLDIR)"
package/go: Add HOST_GO_CGO_ENABLED The go compiler's cgo support uses threads. If BR2_TOOLCHAIN_HAS_THREADS is set, build in cgo support for any go programs that may need it. Note that any target package needing cgo support must include 'depends on BR2_TOOLCHAIN_HAS_THREADS' in its config file. Fixes build errors like these: error: #warning requested reentrant code http://autobuild.buildroot.net/results/42a8d07101d8d954511d1c884ecb66e8d861899e Signed-off-by: Geoff Levand <geoff@infradead.org> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-05-26 20:21:33 +02:00
# The go compiler's cgo support uses threads. If BR2_TOOLCHAIN_HAS_THREADS is
# set, build in cgo support for any go programs that may need it. Note that
# any target package needing cgo support must include
# 'depends on BR2_TOOLCHAIN_HAS_THREADS' in its config file.
package/go: fix cross-compilation settings 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> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Acked-by: Christian Stewart <christian@paral.in>
2017-10-16 19:08:45 +02:00
ifeq ($(BR2_TOOLCHAIN_HAS_THREADS),y)
package/go: Add HOST_GO_CGO_ENABLED The go compiler's cgo support uses threads. If BR2_TOOLCHAIN_HAS_THREADS is set, build in cgo support for any go programs that may need it. Note that any target package needing cgo support must include 'depends on BR2_TOOLCHAIN_HAS_THREADS' in its config file. Fixes build errors like these: error: #warning requested reentrant code http://autobuild.buildroot.net/results/42a8d07101d8d954511d1c884ecb66e8d861899e Signed-off-by: Geoff Levand <geoff@infradead.org> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-05-26 20:21:33 +02:00
HOST_GO_CGO_ENABLED = 1
else
HOST_GO_CGO_ENABLED = 0
endif
package/go: fix building host go toolchain when target isn't supported The go toolchain can cross-compile by default. So most of the time, building a toolchain that supports a target, allows us to also build go binaries for the host. This is how support for host go packages was added: we use the same toolchain that was initially built only for target. But we might want to build a go binary for the host, when compiling a target for which go isn't supported. Then, building host-go will fail: by default, we build go for a specific target, and give the toolchain bootstrap scripts the cross compiler we'll use. This change modifies this behaviour: we only assume the go toolchain is cross-capable if we know the current target is supported. Otherwise this is a simple host go tool. We don't need to set any of the options needed for cross-compilation in that case. Thus, only set all the target-specific go options under a condition that the target arch is supported. The only option we still set is HOST_GO_CGO_ENABLED, and we always set it to enabled. It was also considered to create a separate package to build the go-for-host compiler which would be used for host-go-packages, but that would lead to a lot of duplication and is completely unnecessary. Fixes: http://autobuild.buildroot.net/results/98b9c7aaff2af4d19adfedac00b768d92530ce94 http://autobuild.buildroot.net/results/bed228995ce3778720f991df9b41345a7c724a46 http://autobuild.buildroot.net/results/3b3ea148165b96513ea511ee0d4adb334a6afac8 Signed-off-by: Anisse Astier <anisse@astier.eu> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Reviewed-by: Anisse Astier <anisse@astier.eu> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-04-15 22:49:51 +02:00
HOST_GO_CROSS_ENV = \
CC_FOR_TARGET="$(TARGET_CC)" \
CXX_FOR_TARGET="$(TARGET_CXX)" \
GOARCH=$(GO_GOARCH) \
$(if $(GO_GOARM),GOARM=$(GO_GOARM)) \
GO_ASSUME_CROSSCOMPILING=1
else # !BR2_PACKAGE_HOST_GO_TARGET_ARCH_SUPPORTS
# host-go can still be used to build packages for the host. No need to set all
# the arch stuff since we will not be cross-compiling.
HOST_GO_CGO_ENABLED = 1
endif # BR2_PACKAGE_HOST_GO_TARGET_ARCH_SUPPORTS
package/go: add a HOST_GO_HOST_ENV variable package/go/go.mk provides a HOST_GO_TARGET_ENV which provides a useful set of environment variables needed to build target Go packages. For host packages, we simply have package/pkg-golang.mk defining GO_HOST_ENV to specify CFLAGS/LDFLAGS, but that's it: we don't pass an explicit path to the compiler, we don't pass GO111MODULE, GOCACHE, GOROOT, etc. This commit introduces a HOST_GO_HOST_ENV variable that provides the appropriate set of environment variables to use when building host golang packages. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-08-29 10:58:42 +02:00
# For the convenience of host golang packages
HOST_GO_HOST_ENV = \
package/go: introduce HOST_GO_COMMON_ENV A few variables are common between HOST_GO_TARGET_ENV and HOST_GO_HOST_ENV, so let's introduce a HOST_GO_COMMON_ENV variable for those few common ones (which will increase in follow-up commits). Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-08-29 11:04:25 +02:00
$(HOST_GO_COMMON_ENV) \
package/go: add a HOST_GO_HOST_ENV variable package/go/go.mk provides a HOST_GO_TARGET_ENV which provides a useful set of environment variables needed to build target Go packages. For host packages, we simply have package/pkg-golang.mk defining GO_HOST_ENV to specify CFLAGS/LDFLAGS, but that's it: we don't pass an explicit path to the compiler, we don't pass GO111MODULE, GOCACHE, GOROOT, etc. This commit introduces a HOST_GO_HOST_ENV variable that provides the appropriate set of environment variables to use when building host golang packages. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-08-29 10:58:42 +02:00
GOARCH="" \
GOCACHE="$(HOST_GO_HOST_CACHE)" \
CC="$(HOST_CCNOCCACHE)" \
CXX="$(HOST_CXXNOCCACHE)" \
CGO_CFLAGS="$(HOST_CFLAGS)" \
CGO_CXXFLAGS="$(HOST_CXXFLAGS)" \
CGO_LDFLAGS="$(HOST_LDFLAGS)"
go: cleanup cross-compilation support Now that we fixed cross-compilation in the go package, cleanup the build to remove the workaround added in 60c5c96ae109dcea48e0997b5e6e6645ac9b86 "package/go: Build host tools with host CC". We only need a single pass to build the go toolchain. Signed-off-by: Anisse Astier <anisse@astier.eu> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-05-11 22:50:34 +02:00
# The go build system is not compatible with ccache, so use
package/go: Build host tools with host CC The go build system doesn't have the notion of cross compiling, but just the notion of architecture. When the host and target architectures are different it expects to be given a target cross compiler in CC_FOR_TARGET. When the architectures are the same it will use CC_FOR_TARGET for both host and target compilation. To work around this limitation build and install a set of compiler and tool binaries built with CC_FOR_TARGET set to the host compiler. Also, the go build system is not compatible with ccache, so use HOSTCC_NOCCACHE. See https://github.com/golang/go/issues/11685. Fixes build errors like these: host/usr/bin/go: No such file or directory http://autobuild.buildroot.net/results/6664189a6f3a815978e8d0a1d7ef408ca47e2874/ Signed-off-by: Geoff Levand <geoff@infradead.org> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-05-26 20:21:32 +02:00
# HOSTCC_NOCCACHE. See https://github.com/golang/go/issues/11685.
go: new host package Add a new package 'go' which builds the host cross compiler and libraries for the go programming language. Signed-off-by: Geoff Levand <geoff@infradead.org> [Thomas: - Put the computation of GO_GOARM inside the ifeq ($(BR2_arm),y) condition rather than duplicating this condition. - Remove the GO_GOARCH=unknown case, since there is no way to fall in this case as only supported architectures can use host-go. - Remove the GO_GOARM=unknown case, since we are sure that only ARMv5/6/7 will use host-go. - Rename HOST_GO_FINAL to HOST_GO_ROOT, since it's really the "root" of the Go installation. - Remove visible Config.in.host option.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-04-04 21:31:49 +02:00
HOST_GO_MAKE_ENV = \
go: explicitly disable modules to avoid unintended network lookup Go "modules" refers to the dependency fetching, verification (hashing), and version control system built into Go as of 1.11. It is not desirable to have Go modules enabled in Buildroot in the normal case, as Buildroot manages downloading the sources, and third party dependency managers are typically not used. In the absence of the GO111MODULE environment variable, the Go compiler will correctly compile using the "vendor" version of dependencies downloaded by Buildroot during the compilation process for Go-based packages. However, if the user sets the GO111MODULE=on environment variable, the Go compiler will download the Go dependencies for Buildroot packages, using the modules system. This is potentially unintended behavior from user environment variables. This commit sets the GO111MODULE=off variable in the Go target and host compilation environments, disabling Go modules support for Buildroot mainline packages. Signed-off-by: Christian Stewart <christian@paral.in> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-01-26 11:23:55 +01:00
GO111MODULE=off \
package/go: set GOCACHE to a host path Set the GOCACHE environment variable properly. It was previously unset, and defaults to $HOME/.cache/go-build. Signed-off-by: Christian Stewart <christian@paral.in> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-03-12 06:41:14 +01:00
GOCACHE=$(HOST_GO_HOST_CACHE) \
go: new host package Add a new package 'go' which builds the host cross compiler and libraries for the go programming language. Signed-off-by: Geoff Levand <geoff@infradead.org> [Thomas: - Put the computation of GO_GOARM inside the ifeq ($(BR2_arm),y) condition rather than duplicating this condition. - Remove the GO_GOARCH=unknown case, since there is no way to fall in this case as only supported architectures can use host-go. - Remove the GO_GOARM=unknown case, since we are sure that only ARMv5/6/7 will use host-go. - Rename HOST_GO_FINAL to HOST_GO_ROOT, since it's really the "root" of the Go installation. - Remove visible Config.in.host option.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-04-04 21:31:49 +02:00
GOROOT_BOOTSTRAP=$(HOST_GO_BOOTSTRAP_ROOT) \
GOROOT_FINAL=$(HOST_GO_ROOT) \
GOROOT="$(@D)" \
GOBIN="$(@D)/bin" \
GOOS=linux \
package/go: fix cross-compilation settings 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> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Acked-by: Christian Stewart <christian@paral.in>
2017-10-16 19:08:45 +02:00
CC=$(HOSTCC_NOCCACHE) \
package/go: fixing host go cross compilation Actually if GOHOSTOS == GOOS || GOHOSTARCH == GOARCH the go build system assume it's not cross compiling and uses the same toolchain for both the host and the target. This commit adds a patch to enable the explicit GO_ASSUME_CROSSCOMPILING in go build system and updates to go package accordingly. Fixes: http://autobuild.buildroot.net/results/3636b1ac5756a782fd7578186508aaf9d105e3e9/ http://autobuild.buildroot.net/results/25790dca7e19527bb360d7dfb325cd9cfc3b56cc/ and many more. References: https://github.com/golang/go/issues/25177 https://golang.org/cl/112156 Signed-off-by: Angelo Compagnucci <angelo@amarulasolutions.com> Signed-off-by: Anisse Astier <anisse@astier.eu> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-05-11 22:50:33 +02:00
CXX=$(HOSTCXX_NOCCACHE) \
package/go: fix building host go toolchain when target isn't supported The go toolchain can cross-compile by default. So most of the time, building a toolchain that supports a target, allows us to also build go binaries for the host. This is how support for host go packages was added: we use the same toolchain that was initially built only for target. But we might want to build a go binary for the host, when compiling a target for which go isn't supported. Then, building host-go will fail: by default, we build go for a specific target, and give the toolchain bootstrap scripts the cross compiler we'll use. This change modifies this behaviour: we only assume the go toolchain is cross-capable if we know the current target is supported. Otherwise this is a simple host go tool. We don't need to set any of the options needed for cross-compilation in that case. Thus, only set all the target-specific go options under a condition that the target arch is supported. The only option we still set is HOST_GO_CGO_ENABLED, and we always set it to enabled. It was also considered to create a separate package to build the go-for-host compiler which would be used for host-go-packages, but that would lead to a lot of duplication and is completely unnecessary. Fixes: http://autobuild.buildroot.net/results/98b9c7aaff2af4d19adfedac00b768d92530ce94 http://autobuild.buildroot.net/results/bed228995ce3778720f991df9b41345a7c724a46 http://autobuild.buildroot.net/results/3b3ea148165b96513ea511ee0d4adb334a6afac8 Signed-off-by: Anisse Astier <anisse@astier.eu> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Reviewed-by: Anisse Astier <anisse@astier.eu> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-04-15 22:49:51 +02:00
CGO_ENABLED=$(HOST_GO_CGO_ENABLED) \
$(HOST_GO_CROSS_ENV)
go: new host package Add a new package 'go' which builds the host cross compiler and libraries for the go programming language. Signed-off-by: Geoff Levand <geoff@infradead.org> [Thomas: - Put the computation of GO_GOARM inside the ifeq ($(BR2_arm),y) condition rather than duplicating this condition. - Remove the GO_GOARCH=unknown case, since there is no way to fall in this case as only supported architectures can use host-go. - Remove the GO_GOARM=unknown case, since we are sure that only ARMv5/6/7 will use host-go. - Rename HOST_GO_FINAL to HOST_GO_ROOT, since it's really the "root" of the Go installation. - Remove visible Config.in.host option.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-04-04 21:31:49 +02:00
define HOST_GO_BUILD_CMDS
package/go: fix cross-compilation settings 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> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Acked-by: Christian Stewart <christian@paral.in>
2017-10-16 19:08:45 +02:00
cd $(@D)/src && \
package/go: fix building host go toolchain when target isn't supported The go toolchain can cross-compile by default. So most of the time, building a toolchain that supports a target, allows us to also build go binaries for the host. This is how support for host go packages was added: we use the same toolchain that was initially built only for target. But we might want to build a go binary for the host, when compiling a target for which go isn't supported. Then, building host-go will fail: by default, we build go for a specific target, and give the toolchain bootstrap scripts the cross compiler we'll use. This change modifies this behaviour: we only assume the go toolchain is cross-capable if we know the current target is supported. Otherwise this is a simple host go tool. We don't need to set any of the options needed for cross-compilation in that case. Thus, only set all the target-specific go options under a condition that the target arch is supported. The only option we still set is HOST_GO_CGO_ENABLED, and we always set it to enabled. It was also considered to create a separate package to build the go-for-host compiler which would be used for host-go-packages, but that would lead to a lot of duplication and is completely unnecessary. Fixes: http://autobuild.buildroot.net/results/98b9c7aaff2af4d19adfedac00b768d92530ce94 http://autobuild.buildroot.net/results/bed228995ce3778720f991df9b41345a7c724a46 http://autobuild.buildroot.net/results/3b3ea148165b96513ea511ee0d4adb334a6afac8 Signed-off-by: Anisse Astier <anisse@astier.eu> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Reviewed-by: Anisse Astier <anisse@astier.eu> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-04-15 22:49:51 +02:00
$(HOST_GO_MAKE_ENV) ./make.bash $(if $(VERBOSE),-v)
go: new host package Add a new package 'go' which builds the host cross compiler and libraries for the go programming language. Signed-off-by: Geoff Levand <geoff@infradead.org> [Thomas: - Put the computation of GO_GOARM inside the ifeq ($(BR2_arm),y) condition rather than duplicating this condition. - Remove the GO_GOARCH=unknown case, since there is no way to fall in this case as only supported architectures can use host-go. - Remove the GO_GOARM=unknown case, since we are sure that only ARMv5/6/7 will use host-go. - Rename HOST_GO_FINAL to HOST_GO_ROOT, since it's really the "root" of the Go installation. - Remove visible Config.in.host option.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-04-04 21:31:49 +02:00
endef
define HOST_GO_INSTALL_CMDS
go: cleanup cross-compilation support Now that we fixed cross-compilation in the go package, cleanup the build to remove the workaround added in 60c5c96ae109dcea48e0997b5e6e6645ac9b86 "package/go: Build host tools with host CC". We only need a single pass to build the go toolchain. Signed-off-by: Anisse Astier <anisse@astier.eu> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-05-11 22:50:34 +02:00
$(INSTALL) -D -m 0755 $(@D)/bin/go $(HOST_GO_ROOT)/bin/go
$(INSTALL) -D -m 0755 $(@D)/bin/gofmt $(HOST_GO_ROOT)/bin/gofmt
go: new host package Add a new package 'go' which builds the host cross compiler and libraries for the go programming language. Signed-off-by: Geoff Levand <geoff@infradead.org> [Thomas: - Put the computation of GO_GOARM inside the ifeq ($(BR2_arm),y) condition rather than duplicating this condition. - Remove the GO_GOARCH=unknown case, since there is no way to fall in this case as only supported architectures can use host-go. - Remove the GO_GOARM=unknown case, since we are sure that only ARMv5/6/7 will use host-go. - Rename HOST_GO_FINAL to HOST_GO_ROOT, since it's really the "root" of the Go installation. - Remove visible Config.in.host option.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-04-04 21:31:49 +02:00
Globally replace $(HOST_DIR)/usr/bin with $(HOST_DIR)/bin Since things are no longer installed in $(HOST_DIR)/usr, the callers should also not refer to it. This is a mechanical change with git grep -l '$(HOST_DIR)/usr/bin' | xargs sed -i 's%$(HOST_DIR)/usr/bin%$(HOST_DIR)/bin%g' Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-07-05 13:14:19 +02:00
ln -sf ../lib/go/bin/go $(HOST_DIR)/bin/
ln -sf ../lib/go/bin/gofmt $(HOST_DIR)/bin/
go: new host package Add a new package 'go' which builds the host cross compiler and libraries for the go programming language. Signed-off-by: Geoff Levand <geoff@infradead.org> [Thomas: - Put the computation of GO_GOARM inside the ifeq ($(BR2_arm),y) condition rather than duplicating this condition. - Remove the GO_GOARCH=unknown case, since there is no way to fall in this case as only supported architectures can use host-go. - Remove the GO_GOARM=unknown case, since we are sure that only ARMv5/6/7 will use host-go. - Rename HOST_GO_FINAL to HOST_GO_ROOT, since it's really the "root" of the Go installation. - Remove visible Config.in.host option.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-04-04 21:31:49 +02:00
cp -a $(@D)/lib $(HOST_GO_ROOT)/
mkdir -p $(HOST_GO_ROOT)/pkg
cp -a $(@D)/pkg/include $(@D)/pkg/linux_* $(HOST_GO_ROOT)/pkg/
go: cleanup cross-compilation support Now that we fixed cross-compilation in the go package, cleanup the build to remove the workaround added in 60c5c96ae109dcea48e0997b5e6e6645ac9b86 "package/go: Build host tools with host CC". We only need a single pass to build the go toolchain. Signed-off-by: Anisse Astier <anisse@astier.eu> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-05-11 22:50:34 +02:00
cp -a $(@D)/pkg/tool $(HOST_GO_ROOT)/pkg/
go: new host package Add a new package 'go' which builds the host cross compiler and libraries for the go programming language. Signed-off-by: Geoff Levand <geoff@infradead.org> [Thomas: - Put the computation of GO_GOARM inside the ifeq ($(BR2_arm),y) condition rather than duplicating this condition. - Remove the GO_GOARCH=unknown case, since there is no way to fall in this case as only supported architectures can use host-go. - Remove the GO_GOARM=unknown case, since we are sure that only ARMv5/6/7 will use host-go. - Rename HOST_GO_FINAL to HOST_GO_ROOT, since it's really the "root" of the Go installation. - Remove visible Config.in.host option.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-04-04 21:31:49 +02:00
# There is a known issue which requires the go sources to be installed
# https://golang.org/issue/2775
cp -a $(@D)/src $(HOST_GO_ROOT)/
package/go: Set file timestamp Set all file timestamps to prevent the go compiler from rebuilding any built in packages when programs are built. Signed-off-by: Geoff Levand <geoff@infradead.org> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-05-26 20:21:33 +02:00
# Set all file timestamps to prevent the go compiler from rebuilding any
# built in packages when programs are built.
go: cleanup cross-compilation support Now that we fixed cross-compilation in the go package, cleanup the build to remove the workaround added in 60c5c96ae109dcea48e0997b5e6e6645ac9b86 "package/go: Build host tools with host CC". We only need a single pass to build the go toolchain. Signed-off-by: Anisse Astier <anisse@astier.eu> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-05-11 22:50:34 +02:00
find $(HOST_GO_ROOT) -type f -exec touch -r $(@D)/bin/go {} \;
go: new host package Add a new package 'go' which builds the host cross compiler and libraries for the go programming language. Signed-off-by: Geoff Levand <geoff@infradead.org> [Thomas: - Put the computation of GO_GOARM inside the ifeq ($(BR2_arm),y) condition rather than duplicating this condition. - Remove the GO_GOARCH=unknown case, since there is no way to fall in this case as only supported architectures can use host-go. - Remove the GO_GOARM=unknown case, since we are sure that only ARMv5/6/7 will use host-go. - Rename HOST_GO_FINAL to HOST_GO_ROOT, since it's really the "root" of the Go installation. - Remove visible Config.in.host option.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-04-04 21:31:49 +02:00
endef
$(eval $(host-generic-package))
Reference in New Issue Copy Permalink