From 157d83ebaed300488bc20ab4e39569f1b2c4aa72 Mon Sep 17 00:00:00 2001 From: Dongsu Park Date: Wed, 2 Feb 2022 14:44:10 +0100 Subject: [PATCH] profiles: remove mask for gcc-config 2 As we need to update gcc-config to 2.5, we have to remove the old mask that prevents gcc-config 2 from being installed. --- .../profiles/coreos/base/package.accept_keywords | 3 +-- .../coreos-overlay/profiles/coreos/base/package.mask | 4 ---- 2 files changed, 1 insertion(+), 6 deletions(-) diff --git a/sdk_container/src/third_party/coreos-overlay/profiles/coreos/base/package.accept_keywords b/sdk_container/src/third_party/coreos-overlay/profiles/coreos/base/package.accept_keywords index 2faf3803a0..b29a92c4f8 100644 --- a/sdk_container/src/third_party/coreos-overlay/profiles/coreos/base/package.accept_keywords +++ b/sdk_container/src/third_party/coreos-overlay/profiles/coreos/base/package.accept_keywords @@ -40,9 +40,8 @@ dev-util/checkbashisms # All versions are ~amd64 and not enabled on arm64 =sys-apps/nvme-cli-1.1 ** -# Upgrade to GCC 9.3.0 to support latest glibc builds +# Upgrade to GCC 10.3.0 to support latest glibc builds =sys-devel/binutils-2.37_p1 ~amd64 ~arm64 -=sys-devel/gcc-config-1.9.1 ~amd64 ~arm64 =sys-libs/binutils-libs-2.37_p1 ~amd64 ~arm64 =sys-fs/cryptsetup-2.4.1-r1 ~amd64 ~arm64 diff --git a/sdk_container/src/third_party/coreos-overlay/profiles/coreos/base/package.mask b/sdk_container/src/third_party/coreos-overlay/profiles/coreos/base/package.mask index 8b3218484c..b6be334a2d 100644 --- a/sdk_container/src/third_party/coreos-overlay/profiles/coreos/base/package.mask +++ b/sdk_container/src/third_party/coreos-overlay/profiles/coreos/base/package.mask @@ -11,10 +11,6 @@ # certificate store provided in NSS rather than the Gentoo/Debian package. >=app-misc/ca-certificates-20000000 -# Since version 2, it tries to write liblto symlinks with absolute paths that -# don't work when building for the board root directories. ->=sys-devel/gcc-config-2 - # Overwrite portage-stable mask. We are delaying the transition to # libxcrypt, because we need to figure out how to solve the dep loop # that results from the migration (python -> virtual/libcrypt ->