From: Sam James <sam@gentoo.org>
To: Nick Alcock via DTrace-devel <dtrace-devel@oss.oracle.com>
Cc: dtrace@lists.linux.dev, Nick Alcock <nick.alcock@oracle.com>
Subject: Re: [DTrace-devel] [PATCH] test: testsuite $dt_flags and linker flags problems
Date: Sat, 02 Nov 2024 03:18:31 +0000 [thread overview]
Message-ID: <87v7x6uxvc.fsf@gentoo.org> (raw)
In-Reply-To: <20241101190759.409416-1-nick.alcock@oracle.com> (Nick Alcock via DTrace-devel's message of "Fri, 1 Nov 2024 19:07:59 +0000")
Nick Alcock via DTrace-devel <dtrace-devel@oss.oracle.com> writes:
> The testsuite passes in a $dtrace environment variable: this must
> be an ELF executable because some tests use it in hashbang lines,
> so necessary flags are passed in in a $dt_flags variable which
> must be passed to every dtrace invocation. These flags are largely
> path adjustments (-I etc) pointing DTrace to the in-source-tree
> testsuite or the out-of-tree SDT headers and such things: as such,
> it's unfortunate that a great many invocations were missed and that
> those invocations were largely things like -G that actually *use* -I.
Thanks. I was suspicious of the $dtrace use and I was wanting to audit
these!
prev parent reply other threads:[~2024-11-02 3:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 19:07 [PATCH] test: testsuite $dt_flags and linker flags problems Nick Alcock
2024-11-02 3:18 ` Sam James [this message]
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=87v7x6uxvc.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=dtrace-devel@oss.oracle.com \
--cc=dtrace@lists.linux.dev \
--cc=nick.alcock@oracle.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.