From: Roman Bolshakov <r.bolshakov@yadro.com>
To: <qemu-devel@nongnu.org>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
"Cameron Esfahani" <dirty@apple.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>
Subject: Re: [PATCH v2 3/4] build: Don't make object files for dtrace on macOS
Date: Fri, 24 Jul 2020 20:00:02 +0300 [thread overview]
Message-ID: <20200724170002.GA34804@SPB-NB-133.local> (raw)
In-Reply-To: <20200717093517.73397-4-r.bolshakov@yadro.com>
On Fri, Jul 17, 2020 at 12:35:16PM +0300, Roman Bolshakov wrote:
> dtrace on macOS uses unresolved symbols with a special prefix to define
> probes [1], only headers should be generated for USDT (dtrace(1)). But
> it doesn't support backwards compatible no-op -G flag [2] and implicit
> build rules fail.
>
> 1. https://markmail.org/message/6grq2ygr5nwdwsnb
> 2. https://markmail.org/message/5xrxt2w5m42nojkz
>
> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
> Cc: Cameron Esfahani <dirty@apple.com>
> Signed-off-by: Roman Bolshakov <r.bolshakov@yadro.com>
> ---
> Makefile.objs | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Makefile.objs b/Makefile.objs
> index d22b3b45d7..982f15ba30 100644
> --- a/Makefile.objs
> +++ b/Makefile.objs
> @@ -211,5 +211,7 @@ trace-events-files = $(SRC_PATH)/trace-events $(trace-events-subdirs:%=$(SRC_PAT
> trace-obj-y = trace-root.o
> trace-obj-y += $(trace-events-subdirs:%=%/trace.o)
> trace-obj-$(CONFIG_TRACE_UST) += trace-ust-all.o
> +ifneq ($(CONFIG_DARWIN),y)
> trace-obj-$(CONFIG_TRACE_DTRACE) += trace-dtrace-root.o
> trace-obj-$(CONFIG_TRACE_DTRACE) += $(trace-events-subdirs:%=%/trace-dtrace.o)
> +endif
> --
> 2.26.1
>
An article about DTrace [1] mentions that FreeBSD also doesn't need that:
"On FreeBSD/Mac OS X, you do not have to generate a separate probe
object file for linking. This makes the compilation process much more
straightforward [...]"
I don't know for sure but perhaps "-G" makes dummy object files there.
1. https://www.ibm.com/developerworks/aix/library/au-dtraceprobes.html
Thanks,
Roman
next prev parent reply other threads:[~2020-07-24 17:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 9:35 [PATCH v2 0/4] Add dtrace support on macOS Roman Bolshakov
2020-07-17 9:35 ` [PATCH v2 1/4] scripts/tracetool: Fix dtrace generation for macOS Roman Bolshakov
2020-07-19 13:52 ` Philippe Mathieu-Daudé
2020-07-20 10:50 ` Roman Bolshakov
2020-07-20 10:53 ` Philippe Mathieu-Daudé
2020-07-21 12:33 ` Stefan Hajnoczi
2020-07-17 9:35 ` [PATCH v2 2/4] scripts/tracetool: Use void pointer for vcpu Roman Bolshakov
2020-07-21 12:34 ` Stefan Hajnoczi
2020-07-17 9:35 ` [PATCH v2 3/4] build: Don't make object files for dtrace on macOS Roman Bolshakov
2020-07-21 12:34 ` Stefan Hajnoczi
2020-07-24 17:00 ` Roman Bolshakov [this message]
2020-07-17 9:35 ` [PATCH v2 4/4] net/colo: Match is-enabled probe to tracepoint Roman Bolshakov
2020-07-18 17:58 ` Zhang, Chen
2020-07-20 10:59 ` Roman Bolshakov
2020-07-21 14:06 ` Daniel P. Berrangé
2020-07-29 12:33 ` Roman Bolshakov
2020-07-29 12:34 ` Daniel P. Berrangé
2020-08-05 10:53 ` Stefan Hajnoczi
2020-08-05 18:01 ` Zhang, Chen
2020-07-21 12:36 ` [PATCH v2 0/4] Add dtrace support on macOS Stefan Hajnoczi
2020-08-07 13:00 ` Stefan Hajnoczi
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=20200724170002.GA34804@SPB-NB-133.local \
--to=r.bolshakov@yadro.com \
--cc=berrange@redhat.com \
--cc=dirty@apple.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).