https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: sci-libs/fflas-ffpack-2.4.3 fails to compile. Discovered on: amd64 (internal ref: tinderbox) NOTE: This machine uses a clang/LLVM toolchain. If you think that this issue is strictly related to clang/LLVM please block bug 408963. If you think that this issue is strictly related to the LLD linker, please block bug 731004. This machine uses also GLIBC-2.32. If you think that this issue is strictly related to GLIBC please block bug 736174.
Created attachment 659266 [details] build.log build log and emerge --info
Created attachment 659268 [details] 1-config.log 1-config.log
*** Bug 741510 has been marked as a duplicate of this bug. ***
The problem here (and in #741510) is that somehow, when you built sci-libs/givaro, it became convinced that you were using gcc4, as determined by the AC_COMPILER_NAME macro in https://github.com/linbox-team/givaro/blob/master/macros/debug.m4. As a result, the configure.ac for givaro (https://github.com/linbox-team/givaro/blob/master/configure.ac#L77) appends "-fabi-version=6" to its CXXFLAGS. That gets propagated to the fflas-ffpack and linbox builds, even when you're performing them with clang and not gcc. Since clang doesn't understand -fabi-version=6, those builds fail. Do you have any record of your givaro build? It may have made a mistake in determining that your compiler was gcc4.
Ping, we need some info about another package (sci-libs/givaro) here since that's where the problem originates.
This was back before I was using gcc-10.x; now I can reproduce the issue. It has been fixed upstream in givaro & fflas-ffpack, but not in a way that's easy to backport. A quick Gentoo-specific hack around the issue is incoming.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0986d11b9e8cc6aeee297afc358cf76e53283665 commit 0986d11b9e8cc6aeee297afc358cf76e53283665 Author: Michael Orlitzky <mjo@gentoo.org> AuthorDate: 2021-08-07 16:32:54 +0000 Commit: Michael Orlitzky <mjo@gentoo.org> CommitDate: 2021-08-07 16:35:54 +0000 sci-libs/fflas-ffpack: patch to avoid -fabi-version=6. This is part two of a quick fix to prevent -fabi-version=6 from finding its way into CXXFLAGS with givaro and fflas-ffpack. A better fix is upstream, but difficult to backport. Since in Gentoo we don't support gcc-4.x, I've just deleted the stuff. I've made a new revision because the -fabi-version flags wind up in "fflas-ffpack-config --cflags". Closes: https://bugs.gentoo.org/741434 Package-Manager: Portage-3.0.20, Repoman-3.0.2 Signed-off-by: Michael Orlitzky <mjo@gentoo.org> ....4.3-r1.ebuild => fflas-ffpack-2.4.3-r2.ebuild} | 1 + .../files/fflas-ffpack-2.4.3-no-fabi-version.patch | 31 ++++++++++++++++++++++ 2 files changed, 32 insertions(+) Additionally, it has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ae6b26acdfebbf19c8f8855a63fd86bab3e63b5d commit ae6b26acdfebbf19c8f8855a63fd86bab3e63b5d Author: Michael Orlitzky <mjo@gentoo.org> AuthorDate: 2021-08-07 16:08:09 +0000 Commit: Michael Orlitzky <mjo@gentoo.org> CommitDate: 2021-08-07 16:35:44 +0000 sci-libs/givaro: new revision to eliminate -fabi-version=6. This is just a quick hack directly to the ./configure script to ensure that the current version of givaro doesn't erroneously detect gcc-4.x where none exists. A real fix is already upstreamed, but not in a release, and is not easy to backport. Bug: https://bugs.gentoo.org/741434 Package-Manager: Portage-3.0.20, Repoman-3.0.2 Signed-off-by: Michael Orlitzky <mjo@gentoo.org> sci-libs/givaro/files/givaro-4.1.1-gcc-10.patch | 36 ++++++++++++++++ sci-libs/givaro/givaro-4.1.1-r2.ebuild | 56 +++++++++++++++++++++++++ 2 files changed, 92 insertions(+)
