public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "orbea" <orbea@riseup.net>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/libressl:master commit in: dev-lang/ruby/
Date: Fri, 18 Oct 2024 15:17:48 +0000 (UTC)	[thread overview]
Message-ID: <1729263683.fc40da2ce32ceff9a07855a7ffcca9f1bcead861.orbea@gentoo> (raw)

commit:     fc40da2ce32ceff9a07855a7ffcca9f1bcead861
Author:     orbea <orbea <AT> riseup <DOT> net>
AuthorDate: Fri Oct 18 15:01:23 2024 +0000
Commit:     orbea <orbea <AT> riseup <DOT> net>
CommitDate: Fri Oct 18 15:01:23 2024 +0000
URL:        https://gitweb.gentoo.org/repo/proj/libressl.git/commit/?id=fc40da2c

dev-lang/ruby: sync ::gentoo

Signed-off-by: orbea <orbea <AT> riseup.net>

 dev-lang/ruby/metadata.xml         | 2 +-
 dev-lang/ruby/ruby-3.1.4-r3.ebuild | 5 +++++
 dev-lang/ruby/ruby-3.1.5.ebuild    | 5 +++++
 3 files changed, 11 insertions(+), 1 deletion(-)

diff --git a/dev-lang/ruby/metadata.xml b/dev-lang/ruby/metadata.xml
index cf9a216..628c6c4 100644
--- a/dev-lang/ruby/metadata.xml
+++ b/dev-lang/ruby/metadata.xml
@@ -7,7 +7,7 @@
   </maintainer>
   <use>
     <flag name="rdoc">Install <pkg>dev-ruby/rdoc</pkg> after installing Ruby.</flag>
-    <flag name="systemtap">Enable SystemTAP/DTrace tracing</flag>
+    <flag name="systemtap">Enable SystemTap/DTrace tracing</flag>
   </use>
   <upstream>
     <remote-id type="github">ruby/ruby</remote-id>

diff --git a/dev-lang/ruby/ruby-3.1.4-r3.ebuild b/dev-lang/ruby/ruby-3.1.4-r3.ebuild
index 782ec72..1a027c0 100644
--- a/dev-lang/ruby/ruby-3.1.4-r3.ebuild
+++ b/dev-lang/ruby/ruby-3.1.4-r3.ebuild
@@ -141,6 +141,11 @@ src_configure() {
 	# as it's risky with newer compilers to leave it as it is.
 	append-flags -fno-strict-aliasing
 
+	# Workaround for bug #938302
+	if use systemtap && has_version "dev-debug/systemtap[-dtrace-symlink(+)]" ; then
+		export DTRACE="${BROOT}"/usr/bin/stap-dtrace
+	fi
+
 	# Socks support via dante
 	if use socks5 ; then
 		# Socks support can't be disabled as long as SOCKS_SERVER is

diff --git a/dev-lang/ruby/ruby-3.1.5.ebuild b/dev-lang/ruby/ruby-3.1.5.ebuild
index e9c7419..84bb31d 100644
--- a/dev-lang/ruby/ruby-3.1.5.ebuild
+++ b/dev-lang/ruby/ruby-3.1.5.ebuild
@@ -150,6 +150,11 @@ src_configure() {
 	# as it's risky with newer compilers to leave it as it is.
 	append-flags -fno-strict-aliasing
 
+	# Workaround for bug #938302
+	if use systemtap && has_version "dev-debug/systemtap[-dtrace-symlink(+)]" ; then
+		export DTRACE="${BROOT}"/usr/bin/stap-dtrace
+	fi
+
 	# Socks support via dante
 	if use socks5 ; then
 		# Socks support can't be disabled as long as SOCKS_SERVER is


             reply	other threads:[~2024-10-18 15:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-18 15:17 orbea [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-11 14:29 [gentoo-commits] repo/proj/libressl:master commit in: dev-lang/ruby/ orbea
2024-10-18 15:17 orbea
2024-07-29  1:58 orbea
2024-04-02 18:50 orbea
2024-01-20 15:34 orbea
2024-01-14 15:06 orbea
2023-11-05  3:44 orbea
2023-09-30  2:38 orbea
2023-07-12 19:14 orbea
2023-06-21 16:17 orbea
2023-06-08 18:29 orbea
2023-05-31 15:34 orbea
2023-05-17 16:32 orbea
2023-05-10 21:14 orbea
2022-10-07 21:11 Quentin Retornaz

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=1729263683.fc40da2ce32ceff9a07855a7ffcca9f1bcead861.orbea@gentoo \
    --to=orbea@riseup.net \
    --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