commit: d719ea13be2cd289a371806b226aff218c30f07f
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Jul 30 18:40:12 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Jul 30 18:40:19 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d719ea13
toolchain-funcs.eclass: cleanup obsolete bits in tc-ld-force-bfd
I didn't want to drop this entirely in c26413ae8029f1557aae95b6f8744fc16671fa3b
as I wanted to keep it to just fixing the error I'd made, but I don't see the
point in keeping this now anyway - non-gcc/clang isn't a thing and if it is
I'd hope they'd support -fuse-ld=bfd anyway.
Plus it's an obvious approach if we need it for something else like forcing
an alt linker that isn't bfd anyway, no need for having cruft remaining.
Signed-off-by: Sam James <sam <AT> gentoo.org>
eclass/toolchain-funcs.eclass | 19 -------------------
1 file changed, 19 deletions(-)
diff --git a/eclass/toolchain-funcs.eclass b/eclass/toolchain-funcs.eclass
index 0eca4dde9f36..e28f6148ddc1 100644
--- a/eclass/toolchain-funcs.eclass
+++ b/eclass/toolchain-funcs.eclass
@@ -545,25 +545,6 @@ tc-ld-force-bfd() {
if tc-is-gcc || tc-is-clang ; then
export LDFLAGS="${LDFLAGS} -fuse-ld=bfd"
fi
-
- 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
- # of a problem for Clang as it accepts absolute paths), like was
- # the case for mold.
- #
- # <=gcc-4.7 and <=clang-3.4 require some coercion.
- # Only works if bfd exists.
- if [[ -e ${path_ld} ]] ; then
- local d="${T}/bfd-linker"
- mkdir -p "${d}"
- ln -sf "${path_ld}" "${d}"/ld
- export LDFLAGS="${LDFLAGS} -B${d}"
- else
- die "unable to locate a BFD linker"
- fi
- fi
}
# @FUNCTION: _tc-has-openmp
