From: Paolo Bonzini <pbonzini@redhat.com>
To: Roman Bolshakov <r.bolshakov@yadro.com>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
"Cameron Esfahani" <dirty@apple.com>
Subject: Re: [PATCH] meson: Don't make object files for dtrace on macOS
Date: Tue, 25 Aug 2020 11:20:51 +0200 [thread overview]
Message-ID: <CABgObfZSyKqBs8LP0O7abHCW4Z1tR63PjExuRKo_izRTvCf+bQ@mail.gmail.com> (raw)
In-Reply-To: <20200825090417.GA38400@SPB-NB-133.local>
[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]
Yes, I have already queued it.
Paolo
Il mar 25 ago 2020, 11:04 Roman Bolshakov <r.bolshakov@yadro.com> ha
scritto:
> On Mon, Aug 24, 2020 at 03:24:31PM +0100, Daniel P. Berrangé wrote:
> > On Sun, Aug 23, 2020 at 12:05:47PM +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
> > >
> > > Cc: Daniel P. Berrangé <berrange@redhat.com>
> > > Cc: Cameron Esfahani <dirty@apple.com>
> > > Signed-off-by: Roman Bolshakov <r.bolshakov@yadro.com>
> > > ---
> > > trace/meson.build | 13 ++++++++-----
> > > 1 file changed, 8 insertions(+), 5 deletions(-)
> >
> > Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
> >
>
> Paolo, should it go through your meson-fixes tree?
>
> Regards,
> Roman
>
>
[-- Attachment #2: Type: text/html, Size: 2067 bytes --]
prev parent reply other threads:[~2020-08-25 9:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-23 9:05 [PATCH] meson: Don't make object files for dtrace on macOS Roman Bolshakov
2020-08-24 14:24 ` Daniel P. Berrangé
2020-08-25 9:04 ` Roman Bolshakov
2020-08-25 9:20 ` Paolo Bonzini [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=CABgObfZSyKqBs8LP0O7abHCW4Z1tR63PjExuRKo_izRTvCf+bQ@mail.gmail.com \
--to=pbonzini@redhat.com \
--cc=berrange@redhat.com \
--cc=dirty@apple.com \
--cc=qemu-devel@nongnu.org \
--cc=r.bolshakov@yadro.com \
--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).