diff options
| author | Bruce Ashfield <bruce.ashfield@gmail.com> | 2024-04-26 20:52:43 +0000 |
|---|---|---|
| committer | Bruce Ashfield <bruce.ashfield@gmail.com> | 2024-05-13 22:32:38 -0400 |
| commit | e7a13cbbc39fd61d8192f5d4427111f666c9ab8b (patch) | |
| tree | 86f64d4b7de17cf3e07617381ceefa95df0f3941 /recipes-containers/containerd/containerd-opencontainers/0001-build-don-t-use-gcflags-to-define-trimpath.patch | |
| parent | 89e2b594dcfd0643b84830dce5e7a5e2cbb046cd (diff) | |
| download | meta-virtualization-e7a13cbbc39fd61d8192f5d4427111f666c9ab8b.tar.gz | |
containerd: consolidate to "containerd"
We no longer need the split between container-docker and
containerd-opencontainers and dependent layers have been
given over a year to adapt.
We do keep the provides and rprovides around for a bit
longer, but those will also be removed in the future.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Diffstat (limited to 'recipes-containers/containerd/containerd-opencontainers/0001-build-don-t-use-gcflags-to-define-trimpath.patch')
| -rw-r--r-- | recipes-containers/containerd/containerd-opencontainers/0001-build-don-t-use-gcflags-to-define-trimpath.patch | 32 |
1 files changed, 0 insertions, 32 deletions
diff --git a/recipes-containers/containerd/containerd-opencontainers/0001-build-don-t-use-gcflags-to-define-trimpath.patch b/recipes-containers/containerd/containerd-opencontainers/0001-build-don-t-use-gcflags-to-define-trimpath.patch deleted file mode 100644 index 62580c6c..00000000 --- a/recipes-containers/containerd/containerd-opencontainers/0001-build-don-t-use-gcflags-to-define-trimpath.patch +++ /dev/null | |||
| @@ -1,32 +0,0 @@ | |||
| 1 | From 9174091fa1624dbb09ce812792a4102dff693541 Mon Sep 17 00:00:00 2001 | ||
| 2 | From: Bruce Ashfield <bruce.ashfield@gmail.com> | ||
| 3 | Date: Mon, 12 Sep 2022 15:40:08 -0400 | ||
| 4 | Subject: [PATCH] build: don't use gcflags to define trimpath | ||
| 5 | |||
| 6 | We can pass trimpath in via environment variables. The gcflags | ||
| 7 | definition of trimpath is for older go versions and is using the | ||
| 8 | complete path for trimming. If the variable is captured in the | ||
| 9 | resulting binary, we have a reproducibility and QA issue. | ||
| 10 | |||
| 11 | Upstream-Status: Inappropriate [embedded specific] | ||
| 12 | |||
| 13 | Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> | ||
| 14 | --- | ||
| 15 | Makefile | 1 - | ||
| 16 | 1 file changed, 1 deletion(-) | ||
| 17 | |||
| 18 | diff --git git.orig/Makefile git.orig/Makefile | ||
| 19 | index 4a6c13042..debb57925 100644 | ||
| 20 | --- git.orig/Makefile | ||
| 21 | +++ git.orig/Makefile | ||
| 22 | @@ -130,7 +130,6 @@ TESTFLAGS_RACE= | ||
| 23 | # See Golang issue re: '-trimpath': https://github.com/golang/go/issues/13809 | ||
| 24 | GO_GCFLAGS=$(shell \ | ||
| 25 | set -- ${GOPATHS}; \ | ||
| 26 | - echo "-gcflags=-trimpath=$${1}/src"; \ | ||
| 27 | ) | ||
| 28 | |||
| 29 | BINARIES=$(addprefix bin/,$(COMMANDS)) | ||
| 30 | -- | ||
| 31 | 2.19.1 | ||
| 32 | |||
