From: "Horodniceanu Andrei" <a.horodniceanu@proton.me>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/user/dlang:master commit in: dev-lang/ldc2/
Date: Wed, 24 Jan 2024 20:25:13 +0000 (UTC) [thread overview]
Message-ID: <1706121526.ce1aa5d8fdb60dcd1c08cc1d35cf77fc2998959b.a.horodniceanu@gentoo> (raw)
commit: ce1aa5d8fdb60dcd1c08cc1d35cf77fc2998959b
Author: Horodniceanu Andrei <a.horodniceanu <AT> proton <DOT> me>
AuthorDate: Wed Jan 24 18:21:55 2024 +0000
Commit: Horodniceanu Andrei <a.horodniceanu <AT> proton <DOT> me>
CommitDate: Wed Jan 24 18:38:46 2024 +0000
URL: https://gitweb.gentoo.org/repo/user/dlang.git/commit/?id=ce1aa5d8
dev-lang/ldc2: pass -fno-strict-aliasing
Bug: https://bugs.gentoo.org/show_bug.cgi?id=922590
Signed-off-by: Horodniceanu Andrei <a.horodniceanu <AT> proton.me>
dev-lang/ldc2/{ldc2-1.36.0.ebuild => ldc2-1.36.0-r1.ebuild} | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/dev-lang/ldc2/ldc2-1.36.0.ebuild b/dev-lang/ldc2/ldc2-1.36.0-r1.ebuild
similarity index 91%
rename from dev-lang/ldc2/ldc2-1.36.0.ebuild
rename to dev-lang/ldc2/ldc2-1.36.0-r1.ebuild
index f6837c0..bc995b9 100644
--- a/dev-lang/ldc2/ldc2-1.36.0.ebuild
+++ b/dev-lang/ldc2/ldc2-1.36.0-r1.ebuild
@@ -3,7 +3,7 @@
EAPI=8
-inherit multilib-build cmake llvm
+inherit flag-o-matic multilib-build cmake llvm
MY_PV="${PV//_/-}"
MY_P="ldc-${MY_PV}-src"
@@ -18,7 +18,7 @@ SLOT="$(ver_cut 1-2)/$(ver_cut 3)"
IUSE="static-libs"
-# Upstream supports LLVM 11.0 through 16.0.
+# Upstream supports LLVM 11.0 through 17.0.
DEPEND="
|| (
sys-devel/llvm:17
@@ -53,6 +53,8 @@ d_src_configure() {
# We disable assertions so we have to apply the same workaround as for
# sys-devel/llvm: add -DNDEBUG to CPPFLAGS.
local CPPFLAGS="${CPPFLAGS} -DNDEBUG"
+ # https://bugs.gentoo.org/show_bug.cgi?id=922590
+ append-flags -fno-strict-aliasing
local mycmakeargs=(
-DD_VERSION=2
-DCMAKE_INSTALL_PREFIX=/usr/lib/ldc2/$(ver_cut 1-2)
next reply other threads:[~2024-01-24 20:25 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 20:25 Horodniceanu Andrei [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-14 17:55 [gentoo-commits] repo/user/dlang:master commit in: dev-lang/ldc2/ Horodniceanu Andrei
2024-09-13 9:49 Horodniceanu Andrei
2024-09-13 9:49 Horodniceanu Andrei
2024-09-13 9:49 Horodniceanu Andrei
2024-09-13 9:49 Horodniceanu Andrei
2024-06-02 5:29 Horodniceanu Andrei
2024-05-30 17:28 Horodniceanu Andrei
2024-04-13 23:04 Horodniceanu Andrei
2024-03-13 21:29 Horodniceanu Andrei
2024-03-13 21:29 Horodniceanu Andrei
2024-03-13 21:29 Horodniceanu Andrei
2024-03-13 21:29 Horodniceanu Andrei
2024-03-13 21:29 Horodniceanu Andrei
2024-03-13 21:29 Horodniceanu Andrei
2024-03-13 21:29 Horodniceanu Andrei
2024-03-13 21:29 Horodniceanu Andrei
2024-01-24 20:25 Horodniceanu Andrei
2024-01-14 10:38 Horodniceanu Andrei
2024-01-13 16:26 Horodniceanu Andrei
2024-01-04 14:04 Horodniceanu Andrei
2023-09-28 4:56 Marco Leise
2023-09-28 4:56 Marco Leise
2022-07-25 11:15 Marco Leise
2022-03-24 18:15 Marco Leise
2022-03-24 18:15 Marco Leise
2022-02-06 15:50 Marco Leise
2021-07-07 15:41 Marco Leise
2021-07-07 15:41 Marco Leise
2020-11-16 4:05 Marco Leise
2020-11-16 4:05 Marco Leise
2020-08-15 1:50 Marco Leise
2020-08-15 1:50 Marco Leise
2020-05-17 15:07 Marco Leise
2019-12-23 16:56 Marco Leise
2019-12-23 16:56 Marco Leise
2019-11-30 12: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=1706121526.ce1aa5d8fdb60dcd1c08cc1d35cf77fc2998959b.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