commit: 877403097b5e2779b411ba206132897416c16a4d Author: Andrei Horodniceanu <a.horodniceanu <AT> proton <DOT> me> AuthorDate: Thu Apr 4 22:39:49 2024 +0000 Commit: Horodniceanu Andrei <a.horodniceanu <AT> proton <DOT> me> CommitDate: Sat Apr 13 23:00:59 2024 +0000 URL: https://gitweb.gentoo.org/repo/user/dlang.git/commit/?id=87740309
dev-util/serve-d: Link upstream issue about -mcpu=native with ldc2 Bug: https://github.com/libmir/mir-ion/pull/46 Signed-off-by: Andrei Horodniceanu <a.horodniceanu <AT> proton.me> dev-util/serve-d/serve-d-0.8.0_beta15-r2.ebuild | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/dev-util/serve-d/serve-d-0.8.0_beta15-r2.ebuild b/dev-util/serve-d/serve-d-0.8.0_beta15-r2.ebuild index b06160f..8969b4d 100644 --- a/dev-util/serve-d/serve-d-0.8.0_beta15-r2.ebuild +++ b/dev-util/serve-d/serve-d-0.8.0_beta15-r2.ebuild @@ -113,14 +113,12 @@ src_unpack() { src_configure() { # There's an issue with ldc that when -mcpu=native is specified you - # get an llvm stack trace. I have to investigate it further before - # reporting. -mcpu=<resolve-march-native> works though. For now - # just remove -mcpu=native for ldc2. + # get an llvm stack trace. It seems to be related to the use of + # certain intrinsics that depend on the target cpu. if [[ ${EDC} == ldc2* && ${DCFLAGS} == *-mcpu=native* ]]; then ewarn "-mcpu=native causes issues with ldc2 so it will be removed" - ewarn "from your flags. If you still want to specify it use" - ewarn "app-misc/resolve-march-native to get your actual architecture" - ewarn "and use that with -mcpu, like in -mcpu=znver3." + ewarn "from your flags." + ewarn "See: https://github.com/libmir/mir-ion/pull/46"; fi dlang-filter-dflags "ldc2*" "-mcpu=native"
