lttng-dev.lists.lttng.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi via lttng-dev <lttng-dev@lists.lttng.org>
To: Michael Jeanson <mjeanson@efficios.com>
Cc: lttng-dev <lttng-dev@lists.lttng.org>
Subject: Re: [lttng-dev] [PATCH] Fix: tracepoint.h: define SDT_USE_VARIADIC in pkg-config CFLAGS
Date: Mon, 29 Jun 2020 17:26:00 +0100	[thread overview]
Message-ID: <20200629162600.GA54368@stefanha-x1.localdomain> (raw)
Message-ID: <20200629162600.D5EewI-Oxuu9Db269hAxYBz4FZOXOhgl5Z4Id88f33Q@z> (raw)
In-Reply-To: <1673641132.14590.1593205320791.JavaMail.zimbra@efficios.com>


[-- Attachment #1.1: Type: text/plain, Size: 829 bytes --]

On Fri, Jun 26, 2020 at 05:02:00PM -0400, Michael Jeanson wrote:
> I proposed a patch here[1] that addresses this problem in a generic way by
> duplicating the macro and namespacing it under LTTNG_. Honestly this is more
> of an sdt bug, the STAP_PROBEV should be in it's own include guard outside
> of _SYS_SDT_H or in it's own header file but we have to work with what's there.
> 
> Can you have a look at the patch and confirm that it fixes your problem?

Great, glad there is already a fix under review.

When I try out the patch the application does not compile. The error
messages are the same as without the patch because _LTTNG_SDT_PROBE() is
not defined. Was that supposed to be _SDT_PROBE() instead?

The application compiles successfully after replacing _LTTNG_SDT_PROBE()
with _SDT_PROBE().

Stefan

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 156 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

  parent reply	other threads:[~2020-06-29 16:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-24 16:09 [PATCH] Fix: tracepoint.h: define SDT_USE_VARIADIC in pkg-config CFLAGS Stefan Hajnoczi via lttng-dev
2020-06-24 16:09 ` [lttng-dev] " Stefan Hajnoczi via lttng-dev
2020-06-26 21:02 ` Michael Jeanson via lttng-dev
2020-06-26 21:02   ` [lttng-dev] " Michael Jeanson via lttng-dev
2020-06-29 16:26   ` Stefan Hajnoczi via lttng-dev [this message]
2020-06-29 16:26     ` Stefan Hajnoczi via lttng-dev
2020-06-29 16:36     ` Michael Jeanson via lttng-dev
2020-06-29 16:36       ` [lttng-dev] " Michael Jeanson via lttng-dev
2020-06-30  9:05       ` Stefan Hajnoczi via lttng-dev
2020-06-30  9:05         ` [lttng-dev] " Stefan Hajnoczi via lttng-dev

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=20200629162600.GA54368@stefanha-x1.localdomain \
    --to=lttng-dev@lists.lttng.org \
    --cc=mjeanson@efficios.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).