From nobody Mon Sep 06 01:36:17 2021 X-Original-To: ruby@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 01695179F430 for ; Mon, 6 Sep 2021 01:36:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4H2rb46H9cz3hnx for ; Mon, 6 Sep 2021 01:36:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id B29B8161AD for ; Mon, 6 Sep 2021 01:36:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 1861aGdb052342 for ; Mon, 6 Sep 2021 01:36:16 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 1861aGks052340 for ruby@FreeBSD.org; Mon, 6 Sep 2021 01:36:16 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: ruby@FreeBSD.org Subject: [Bug 257525] lang/ruby26: add DTRACE option Date: Mon, 06 Sep 2021 01:36:17 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: swills@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ruby@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback- maintainer-feedback? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: FreeBSD-specific Ruby discussions List-Archive: https://lists.freebsd.org/archives/freebsd-ruby List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ruby@freebsd.org X-BeenThere: freebsd-ruby@freebsd.org MIME-Version: 1.0 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D257525 --- Comment #5 from Steve Wills --- (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://git= hub.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=3Dllvm12 WITHOUT_CLANG=3Dyes WITHOUT_CLANG_BOOTSTRAP=3Dyes WITHOUT_LLD=3Dyes WITHOUT_LLD_BOOTSTRAP=3Dyes WITHOUT_LLDB=3Dyes WITHOUT_LLVM_COV=3Dyes 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 encounteri= ng 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 bett= er 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. --=20 You are receiving this mail because: You are the assignee for the bug.=