commit: c26413ae8029f1557aae95b6f8744fc16671fa3b Author: Sam James <sam <AT> gentoo <DOT> org> AuthorDate: Sun Jul 30 18:28:23 2023 +0000 Commit: Sam James <sam <AT> gentoo <DOT> org> CommitDate: Sun Jul 30 18:29:25 2023 +0000 URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c26413ae
toolchain-funcs.eclass: fix tc-force-bfd Before c4e911da66c918bd0944d1457776b82260657cd6, fallback would be false for newer GCC and Clang, not true. Thanks to parona for giving the nudge. Closes: https://bugs.gentoo.org/911503 Fixes: c4e911da66c918bd0944d1457776b82260657cd6 Signed-off-by: Sam James <sam <AT> gentoo.org> eclass/toolchain-funcs.eclass | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/eclass/toolchain-funcs.eclass b/eclass/toolchain-funcs.eclass index e194342f7bb5..26b7a0772ca6 100644 --- a/eclass/toolchain-funcs.eclass +++ b/eclass/toolchain-funcs.eclass @@ -542,12 +542,11 @@ tc-ld-force-bfd() { [[ -e ${path_ld} ]] && export LD=${bfd_ld} # Set up LDFLAGS to select bfd based on the gcc / clang version. - local fallback="true" if tc-is-gcc || tc-is-clang ; then export LDFLAGS="${LDFLAGS} -fuse-ld=bfd" fi - if [[ ${fallback} == "true" ]] ; then + if false ; then # TODO: Clean this up, or is it useful for when the compiler can't # be detected or for rubbish shims? Might be helpful for cases like # when porting to new linker which GCC doesn't yet recognise (less
