From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: profiles/features/llvm/
Date: Thu, 24 Aug 2023 23:15:16 +0000 (UTC) [thread overview]
Message-ID: <1692918788.5e5c9d5c524871f5af260557dbd2962b8eec5087.sam@gentoo> (raw)
commit: 5e5c9d5c524871f5af260557dbd2962b8eec5087
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Thu Aug 24 23:13:08 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Aug 24 23:13:08 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5e5c9d5c
profiles/features/llvm: drop problematic LDFLAGS
clang-common already handles setting these for us, and if we set it in profiles,
then it gets passed down to gcc via clang for things like Fortran where clang
is just acting as the driver.
Closes: https://bugs.gentoo.org/908798
Signed-off-by: Sam James <sam <AT> gentoo.org>
profiles/features/llvm/make.defaults | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/profiles/features/llvm/make.defaults b/profiles/features/llvm/make.defaults
index a677172b269d..ce3401222615 100644
--- a/profiles/features/llvm/make.defaults
+++ b/profiles/features/llvm/make.defaults
@@ -11,7 +11,10 @@ CXX="clang++"
LD="ld.lld"
# linker flags
-LDFLAGS="${LDFLAGS} -fuse-ld=lld -rtlib=compiler-rt -unwindlib=libunwind -Wl,--as-needed"
+# We don't set LDFLAGS here for linker, rtlib, etc because clang-common enforces
+# the needed bits for us and it confuses clang->gcc for stuff like Fortran,
+# see bug #908798.
+LDFLAGS="${LDFLAGS} -Wl,--as-needed"
# use LLVM-provided binutils
AR="llvm-ar"
next reply other threads:[~2023-08-24 23:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 23:15 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-22 5:58 [gentoo-commits] repo/gentoo:master commit in: profiles/features/llvm/ Jimi Huotari
2024-08-19 14:36 Andreas K. Hüttel
2024-06-01 17:27 Michał Górny
2024-05-08 10:16 Sam James
2023-08-20 13:37 Joonas Niilola
2023-08-20 6:14 Sam James
2023-08-19 5:31 Joonas Niilola
2023-08-14 16:39 Ionen Wolkens
2023-08-13 19:45 Ionen Wolkens
2023-08-11 10:52 Ionen Wolkens
2023-06-22 1:51 Sam James
2023-03-03 22:22 Sam James
2023-03-03 22:04 Sam James
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1692918788.5e5c9d5c524871f5af260557dbd2962b8eec5087.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox