Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 06 Sep 2021 15:28:59 +0000
From:      bugzilla-noreply@freebsd.org
To:        ruby@FreeBSD.org
Subject:   [Bug 257525] lang/ruby26: add DTRACE option
Message-ID:  <bug-257525-21402-73l8mJcflN@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-257525-21402@https.bugs.freebsd.org/bugzilla/>
References:  <bug-257525-21402@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D257525

--- Comment #11 from Steve Wills <swills@FreeBSD.org> ---
(In reply to Evgeniy Khramtsov from comment #10)

> Seems that dtrace calls "ld" regardless of what is set as LD in /usr/shar=
e/mk/sys.mk. LD set via env(1) is also ignored. Maybe a base issue?

Thank you, yes, this is the cause of the issue and what I was trying to get=
 to.
Indeed, dtrace expects an "ld" command:

https://cgit.freebsd.org/src/tree/cddl/contrib/opensolaris/lib/libdtrace/co=
mmon/dt_open.c#n789

It would be nice if it checked LD environment variable, and we can file a b=
ug
requesting that, but expecting an "ld" command to exist somewhere seems lik=
e a
pretty reasonable expectation to me.

I'm not even sure where the right place to file a bug on dtrace would be. W=
hat
is the upstream source? Or perhaps it should be filed against FreeBSD base
since this was added here:

https://cgit.freebsd.org/src/commit/cddl/contrib/opensolaris/lib/libdtrace/=
common/dt_open.c?id=3Dfb24b944be9a0a5c0fe8a09b28321d1ff2c245fd

Seems like there are a number of ways around the issue for now.

You could patch this hard coded path in your setup for now, since you've
already patched so many other things. Or perhaps create a patch to dtrace to
have it check LD environment variable and fall back to "ld" and add that to=
 a
dtrace bug report. But, since we now understand the issue and disabling dtr=
ace
in the port avoids it and also helps with reproducibility, I'm OK with the
patch to ruby to add the DTRACE option.

Thanks again for the help understanding the issue. I'll try to file a bug
against FreeBSD base and create a patch when I have some time.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-257525-21402-73l8mJcflN>