From: "Horodniceanu Andrei" <a.horodniceanu@proton.me>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/user/dlang:master commit in: x11-terms/tilix/
Date: Sun, 2 Jun 2024 05:29:09 +0000 (UTC) [thread overview]
Message-ID: <1717260841.82a9bfa278c2d1b2828a59ae59f7a4e096c63ef4.a.horodniceanu@gentoo> (raw)
commit: 82a9bfa278c2d1b2828a59ae59f7a4e096c63ef4
Author: Andrei Horodniceanu <a.horodniceanu <AT> proton <DOT> me>
AuthorDate: Sat Jun 1 04:27:48 2024 +0000
Commit: Horodniceanu Andrei <a.horodniceanu <AT> proton <DOT> me>
CommitDate: Sat Jun 1 16:54:01 2024 +0000
URL: https://gitweb.gentoo.org/repo/user/dlang.git/commit/?id=82a9bfa2
x11-terms/tilix: let meson handle LDFLAGS for dmd and ldc2
Meson is too eager to transform the already transformed by the eclass
LDFLAGS from gcc-style (-Wl, prefixed) to dmd-style (-L prefixed). This
leads to flags receiving a double prefix. Specifically
-Wl,-z,pack-relative-relocs is transformed by the eclass into -L-z
-Lpack-relative-relocs which meson then transforms into -L-z
-L=-Lpack-relative-relocs making it ignore the flag and swallow the next
one. If meson is given the raw LDFLAGS it will transform them properly.
Additionally, don't specify DCFLAGS in the linker arguments, meson will
add them by default anyway.
Signed-off-by: Andrei Horodniceanu <a.horodniceanu <AT> proton.me>
x11-terms/tilix/tilix-1.9.6-r2.ebuild | 16 +++++++++++++++-
1 file changed, 15 insertions(+), 1 deletion(-)
diff --git a/x11-terms/tilix/tilix-1.9.6-r2.ebuild b/x11-terms/tilix/tilix-1.9.6-r2.ebuild
index 5707050..d1d66cc 100644
--- a/x11-terms/tilix/tilix-1.9.6-r2.ebuild
+++ b/x11-terms/tilix/tilix-1.9.6-r2.ebuild
@@ -50,7 +50,21 @@ BDEPEND="
"
src_configure() {
- DFLAGS="${DCFLAGS}" meson_src_configure -Dd_link_args="${DCFLAGS} ${DLANG_LDFLAGS}"
+ # meson is very strict in how he expects the linker flags. It
+ # modifies our flags from:
+ # -Lz -Lpack-relative-relocs
+ # to:
+ # -Lz -L=-Lpack-relative-relocs
+ #
+ # Note that specyfing -L=z -L=pack-relative-relocs is still not enough
+ # as meson modifies the second argument again.
+ #
+ # This only works so long as the eclass doesn't add any extra flags
+ # for dmd or ldc (it does for gdc).
+ local largs
+ [[ ${EDC} != gdc* ]] && largs="${LDFLAGS}" || largs="${DLANG_LDFLAGS}"
+
+ DFLAGS="${DCFLAGS}" meson_src_configure -Dd_link_args="${largs}"
}
pkg_postinst() {
next reply other threads:[~2024-06-02 5:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-02 5:29 Horodniceanu Andrei [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-03 20:34 [gentoo-commits] repo/user/dlang:master commit in: x11-terms/tilix/ Horodniceanu Andrei
2024-08-30 7:58 Horodniceanu Andrei
2024-06-02 5:29 Horodniceanu Andrei
2024-06-02 5:29 Horodniceanu Andrei
2024-06-02 5:29 Horodniceanu Andrei
2024-06-02 5:29 Horodniceanu Andrei
2024-06-02 5:29 Horodniceanu Andrei
2024-04-13 23:04 Horodniceanu Andrei
2024-03-13 21:29 Horodniceanu Andrei
2024-01-14 10:37 Horodniceanu Andrei
2024-01-14 10:37 Horodniceanu Andrei
2023-12-18 12:37 Horodniceanu Andrei
2022-05-10 12:52 Marco Leise
2020-08-15 18:01 Marco Leise
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=1717260841.82a9bfa278c2d1b2828a59ae59f7a4e096c63ef4.a.horodniceanu@gentoo \
--to=a.horodniceanu@proton.me \
--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