From 068424b26532f3551a81421a9be67ed206e5c11a Mon Sep 17 00:00:00 2001 From: V3n3RiX Date: Wed, 11 Aug 2021 07:02:28 +0100 Subject: gentoo resync : 11.08.2021 --- sci-libs/givaro/files/givaro-4.1.1-gcc-10.patch | 36 +++++++++++++++++++++++++ 1 file changed, 36 insertions(+) create mode 100644 sci-libs/givaro/files/givaro-4.1.1-gcc-10.patch (limited to 'sci-libs/givaro/files/givaro-4.1.1-gcc-10.patch') diff --git a/sci-libs/givaro/files/givaro-4.1.1-gcc-10.patch b/sci-libs/givaro/files/givaro-4.1.1-gcc-10.patch new file mode 100644 index 000000000000..0564c7f94fef --- /dev/null +++ b/sci-libs/givaro/files/givaro-4.1.1-gcc-10.patch @@ -0,0 +1,36 @@ +From 5ba9fa4930b347aea8817da444bea5a88971079a Mon Sep 17 00:00:00 2001 +From: Michael Orlitzky +Date: Sat, 7 Aug 2021 11:43:29 -0400 +Subject: [PATCH 1/1] configure: hack out old GCC-4.x test. + +The Givaro ./configure script fails to detect modern versions of GCC, +instead deciding that they must be gcc-4.8. As a result, we wind up +with "-fabi-version=6" in CXXFLAGS, which then gets propagated to +users of "givaro-config --cflags", like fflas-ffpack. + +This is already fixed upstream, but not in a release, and not in a +way that I care to backport. Here we just hack the configure script +directly since the change is so trivial. +--- + configure | 5 ----- + 1 file changed, 5 deletions(-) + +diff --git a/configure b/configure +index 1eb75b0..f3bbb52 100755 +--- a/configure ++++ b/configure +@@ -17172,11 +17172,6 @@ fi + + echo "-----------------------------------------------" + +-if test "x$CCNAM" = "xgcc48"; then : +- REQUIRED_FLAGS="${REQUIRED_FLAGS} -fabi-version=6" +-fi +- +- + + # Machine characteristics + +-- +2.31.1 + -- cgit v1.2.3