linux/poky.git/meta/classes/go.bbclass, branch uninative-2.6

go: Exclude vcs files when installing deps

2019-05-08T11:15:17+00:00

Because our clones use the host git, on (say) Ubuntu 18.04, the local git directories acquire perl scripts such as fsmonitor-watchman.sample. During packaging, this leads to failures: ERROR: go-hsperfdata-1.0.3+gitAUTOINC+b58598ac84-r0 do_package_qa: QA Issue: /usr/lib/go/pkg/dep/sources/https---github.com-nsf-termbox--go/.git/hooks/fsmonitor-watchman.sample contained in package go-hsperfdata-staticdev requires /usr/bin/perl, but no providers found in RDEPENDS_go-hsperfdata-staticdev? [file-rdeps] ERROR: go-hsperfdata-1.0.3+gitAUTOINC+b58598ac84-r0 do_package_qa: QA run found fatal errors. Please consider fixing them. ERROR: go-hsperfdata-1.0.3+gitAUTOINC+b58598ac84-r0 do_package_qa: ERROR: go-hsperfdata-1.0.3+gitAUTOINC+b58598ac84-r0 do_package_qa: Function failed: do_package_qa (From OE-Core rev: 2ee246524ab881d57d8aac204f671215a25a58d3) Signed-off-by: Alex Kiernan Signed-off-by: Richard Purdie

go.bbclass: Remove unused override

2019-04-12T08:29:06+00:00

The x86 override means the i586 one isn't necessary. (From OE-Core rev: 1658bf2dbdfe1a5b38efcc03359c9937506c120c) Signed-off-by: Mark Asselstine Signed-off-by: Richard Purdie

go.bbclass: Export more GO* environment variables

2019-04-10T12:46:17+00:00

Currently we are not doing a good job of consolidating GO environment variables used by the go build system in the go.bbclass, instead we are relying on the individual GO recipe authors to perform the exports. This can result in inconsistent build results and often binaries that are not properly cross compiled, resulting in segfaults when the applications are run on the target. For example the GO documentation recommends that the environment include a value assigned to GOARM when cross building for ARMv5, ARMv6 and ARMv7 (https://github.com/golang/go/wiki/GoArm). In order to avoid polluting the build scripts with unnecessary exports, such as run.do_compile, we attempt to only export variables when they apply to a specific arch. (From OE-Core rev: 6300c4a83f7c8fc88702798ffe25bd6d57091673) Signed-off-by: Mark Asselstine Signed-off-by: Richard Purdie

go: Add recipes for 1.12 release and make it default

2019-03-09T14:43:11+00:00

- Refresh patches - Enable GOCACHE required as of Go 1.12 (From OE-Core rev: f559fd6df2978f9093672794420eada2b7452987) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

go: Change from TARGET_ARCH to TUNE_PKGARCH

2018-11-07T23:08:55+00:00

Right now go-cross is changing signatures when you change TUNE for a given architecture. In particular this breaks layer tests like: yocto-check-layer ../meta-yocto-bsp/ --machines qemuarm beaglebone-yocto This changes the PN addtion to something containing the tune rather than the arch which avoids these kinds of errors. If go-cross can be tune independent that would be nice but currently that isn't the case. [YOCTO #12586] (From OE-Core rev: e3c7e1703499e6a5332d9ab8a941671ec8235c4f) Signed-off-by: Richard Purdie

go.bbclass: Add -buildmode=pie for non mips arch

2018-10-01T12:04:50+00:00

Fixed QA issue like: WARNING: runc-docker do_package_qa: QA Issue: ELF binary '/path/to/runc-docker/usr/bin/runc' has relocations in .text [textrel] (From OE-Core rev: 8dcd4e6e791c3a8b8bf5e69dca9bb9c887231d69) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

go.bbclass, goarch.bbclass: update SECURITY_CFLAGS

2018-03-06T14:43:10+00:00

With go1.10 the NOPIE flags are only required for MIPS target builds, and are now incompatible for the other architectures. (From OE-Core rev: f2ff90eb7d27a2f69f5948fa8c301de30f5c8132) Signed-off-by: Matt Madison Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

go.bbclass: ptest cleanup and improvements

2018-03-06T14:43:10+00:00

* Don't enable verbose test output (-test.v) by default, as it generates too much noise for automated results parsing * Override do_install_ptest_base in the bbclass, so recipes can provide their own modifications with do_install_ptest. * Improve the generated run-ptest script to better handle large numbers of tests, and to generate 'status: test name' output similar to Automake tests. * Install all non-vendored 'testdata' directories from the source into the ptest package, as some packages share test data among multiple tests. (From OE-Core rev: 11037462d80cefbee90a69e6a8a95895375ed6da) Signed-off-by: Matt Madison Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

go.bbclass: don't stage test data with sources

2018-03-06T14:43:10+00:00

Any directory in a Go package's source tree called 'testdata' contains test data, and isn't necessary for building. Some packages include ELF files and other binaries as test data, and staging them in the sysroot and -dev package leads to unnecessary QA warnings. (From OE-Core rev: b013db7ab58d4d56ad5c6e54a3a32df31aaf8809) Signed-off-by: Matt Madison Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

go.bbclass: remove debug-related commands

2018-03-06T14:43:10+00:00

The 'go env' in the do_compile function and the set -x/+x in the do_install_ptest function were used for debugging the bbclass, and aren't really needed. (From OE-Core rev: 351e9fc39408e094bbb4beedf51221adc8afd143) Signed-off-by: Matt Madison Signed-off-by: Ross Burton Signed-off-by: Richard Purdie