linux/meta-virtualization.git/recipes-containers/riddler/riddler_git.bb, branch kirkstone

riddler: adjust GOROOT, CGO_CFLAGS and CGO_LDFALGS

2022-06-20T16:09:51+00:00

Adjust the GOROOT setting as directory specified by the original one does not exist. The CGO_CFLAGS and CGO_LDFLAGS should use target flags instead of the nativesdk ones. Signed-off-by: Chen Qi Signed-off-by: Bruce Ashfield

global: convert github SRC_URIs to use https protocol

2021-11-02T13:57:03+00:00

github is removing git:// access, and fetches will start experiencing interruptions in service, and eventually will fail completely. bitbake will also begin to warn on github src_uri's that don't use https. So we convert the meta-virt instances to use protocol=https (done using the oe-core contrib conversion script) Signed-off-by: Bruce Ashfield

global: overrides syntax conversion

2021-08-02T21:17:53+00:00

OEcore/bitbake are moving to use the clearer ":" as an overrides separator. This is pass one of updating the meta-virt recipes to use that syntax. This has only been minimally build/runtime tested, more changes will be required for missed overrides, or incorrect conversions Note: A recent bitbake is required: commit 75fad23fc06c008a03414a1fc288a8614c6af9ca Author: Richard Purdie Date: Sun Jul 18 12:59:15 2021 +0100 bitbake: data_smart/parse: Allow ':' characters in variable/function names It is becomming increasingly clear we need to find a way to show what is/is not an override in our syntax. We need to do this in a way which is clear to users, readable and in a way we can transition to. The most effective way I've found to this is to use the ":" charater to directly replace "_" where an override is being specified. This includes "append", "prepend" and "remove" which are effectively special override directives. This patch simply adds the character to the parser so bitbake accepts the value but maps it back to "_" internally so there is no behaviour change. This change is simple enough it could potentially be backported to older version of bitbake meaning layers using the new syntax/markup could work with older releases. Even if other no other changes are accepted at this time and we don't backport, it does set us on a path where at some point in future we could require a more explict syntax. I've tested this patch by converting oe-core/meta-yocto to the new syntax for overrides (9000+ changes) and then seeing that builds continue to work with this patch. (Bitbake rev: 0dbbb4547cb2570d2ce607e9a53459df3c0ac284) Signed-off-by: Richard Purdie Signed-off-by: Bruce Ashfield

riddler: export GO111MODULE=off

2021-03-04T13:33:46+00:00

With the latest go version bump in oe-core export GO111MODULE is on by default. Our build is not setup to use go modules, so we disable it and avoid configuration errors: no required module provides package ... : working directory is not part of a module Signed-off-by: Bruce Ashfield

riddler: fix 32bit ARM build

2020-07-01T16:43:16+00:00

With oe-core commit c23f9e80492e4b [tcmode-default: use go-binary-native by default], we must explictly call the proper cross go binary, versus just the go-native variant. These builds were working by luck, since the go compiler was capable of building the target binaries previously (in its build-from-source creation). We fixup the calls and we no longer see fpu build issues: fatal error: gnu/stubs-soft.h: No such file or directory 7 | # include | ^~~~~~~~~~~~~~~~~~ Signed-off-by: Bruce Ashfield

riddler: do not try to build for mips

2019-02-06T20:51:00+00:00

This recipe does not build for mips, so set COMPATIBLE_HOST to avoid that. Signed-off-by: Joe Slater Signed-off-by: Bruce Ashfield

nets, docker, runc, oci-*tools: go.bbclass compile fixes

2017-09-14T13:49:00+00:00

Recently in the oe-core the go.bbclass changed and requires the defition of the GO_IMPORT variable. This was intended to simplify how the compilation works with go packages and it is still a work in progress. This patch set makes the recipes compatible to generate the same end result as before using the new go.bbclass from oe-core. Any patches that were included in the recipes had to have the paths adjusted because the new go.bbclass manipulates the notion of S to be S + "src" + "$GO_IMPORT" internally for the purpose of unpack, patch and compile. Signed-off-by: Jason Wessel Signed-off-by: Bruce Ashfield

housekeeping: swap out go-osarchmap in favor of goarch

2017-04-12T03:09:01+00:00

Continue work to use go infra in oe-core instead of the support for go previously found in meta-virt. This is a 1:1 drop in replacement and removes one more go piece from meta-virt in favor of the common support found in oe-core. Signed-off-by: Mark Asselstine Signed-off-by: Bruce Ashfield

recipes-containers: set GOROOT

2017-03-21T12:22:32+00:00

Signed-off-by: Khem Raj Signed-off-by: Bruce Ashfield

go: replace explicit go-cross* with inherit go bbclass

2017-03-21T03:15:01+00:00

Rather than expliciting depending on go-cross-${TARGET_ARCH}, we can now simply inherit the oe-core go bbclass. This gets us the correct go dependencies and other variables properly set. Signed-off-by: Bruce Ashfield