[Bug 257525] lang/ruby26: add DTRACE option

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257525

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

> dtrace does exist on such a system, but the port can't link DTRACE using non-base toolchain.

Why not? What is the error? Was it posted previously and I'm missing it?

> Base toolchain links symbols that ports toolchain can't, e.g. https://github.com/DankBSD/ports/commit/fef8031

Sorry, I don't understand. The linked commit doesn't seem to explain much.

I really don't understand this issue overall. It seems like it would really be
helpful if you could be more specific about the issue(s) you seem to be
encountering.

You seem to be saying that you have set these options in src.conf:

CROSS_TOOLCHAIN=llvm12
WITHOUT_CLANG=yes
WITHOUT_CLANG_BOOTSTRAP=yes
WITHOUT_LLD=yes
WITHOUT_LLD_BOOTSTRAP=yes
WITHOUT_LLDB=yes
WITHOUT_LLVM_COV=yes

and an additional patch to enable using external LLVM toolchain. What isn't
clear is why you are doing that, or exactly what problem you are encountering
due to this configuration. Perhaps if you could post the error message and/or
full build log you get when trying to build ruby with this configuration it
might help?

I can say that ruby should be made reproducible if it isn't, in my opinion. I
suggest using sysutils/py-diffoscope to investigate what is changing between
builds; I've used it in the past and it's quite nice.

I wouldn't suggest invoking maintainer timeout here until the issue is better
understood. Maybe someone besides me understands it better. True the option to
disable DTRACE is harmless, at the same time, we try not to add unnecessary
options as each one adds a maintenance work in the long term. I'd apply the
same logic to similarly filed DTRACE option patches.

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