From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-debug/dtrace/
Date: Wed, 30 Oct 2024 22:50:25 +0000 (UTC) [thread overview]
Message-ID: <1730328604.0ccd18bf8c3474e3a01d6052ddc5e05d8dceef5b.sam@gentoo> (raw)
commit: 0ccd18bf8c3474e3a01d6052ddc5e05d8dceef5b
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Oct 30 22:49:43 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Oct 30 22:50:04 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0ccd18bf
dev-debug/dtrace: update live for _FORTIFY_SOURCE fix
Bug: https://github.com/oracle/dtrace-utils/issues/78
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-debug/dtrace/dtrace-9999.ebuild | 3 ---
1 file changed, 3 deletions(-)
diff --git a/dev-debug/dtrace/dtrace-9999.ebuild b/dev-debug/dtrace/dtrace-9999.ebuild
index 63360b80ca91..a1e12159ab4c 100644
--- a/dev-debug/dtrace/dtrace-9999.ebuild
+++ b/dev-debug/dtrace/dtrace-9999.ebuild
@@ -116,9 +116,6 @@ src_configure() {
tc-export CC
- # https://github.com/oracle/dtrace-utils/issues/78
- tc-enables-fortify-source && append-cppflags -U_FORTIFY_SOURCE
-
# lld does this by default, so fix that, although lld fails anyway...
# 'LIBDTRACE_1.0' to symbol 'dtrace_provider_modules' failed: symbol not defined
append-ldflags $(test-flags-CCLD -Wl,--undefined-version)
next reply other threads:[~2024-10-30 22:50 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 22:50 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-25 8:14 [gentoo-commits] repo/gentoo:master commit in: dev-debug/dtrace/ Sam James
2025-03-08 8:41 Arthur Zamarin
2025-03-08 1:41 Sam James
2025-02-05 1:12 Sam James
2024-10-30 22:50 Sam James
2024-10-30 22:50 Sam James
2024-10-30 22:50 Sam James
2024-10-24 8:22 Arthur Zamarin
2024-10-24 2:37 Sam James
2024-09-12 1:06 Sam James
2024-09-12 0:43 Sam James
2024-09-12 0:42 Sam James
2024-09-12 0:42 Sam James
2024-09-12 0:38 Sam James
2024-09-12 0:38 Sam James
2024-09-12 0:30 Sam James
2024-09-12 0:10 Sam James
2024-09-11 23:59 Sam James
2024-09-11 3:35 Sam James
2024-09-10 13:58 Sam James
2024-08-30 18:13 Sam James
2024-08-25 18:49 Sam James
2024-08-22 12:54 Sam James
2024-08-22 12:36 Sam James
2024-08-22 12:36 Sam James
2024-08-22 12:22 Sam James
2024-08-20 1:49 Sam James
2024-08-20 1:49 Sam James
2024-08-20 1:49 Sam James
2024-08-19 23:27 Sam James
2024-08-19 20:16 Sam James
2024-08-18 22:59 Sam James
2024-08-18 21:47 Sam James
2024-08-18 21:42 Sam James
2024-08-18 21:36 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=1730328604.0ccd18bf8c3474e3a01d6052ddc5e05d8dceef5b.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