From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [ltt-dev] SystemTAP support in tracepoints
Date: Wed, 13 Apr 2011 11:38:09 -0400 [thread overview]
Message-ID: <BLU0-SMTP6649154A1D0EEA973E63C396AA0@phx.gbl> (raw)
In-Reply-To: <1302635527.4057.9.camel@springer.wildebeest.org>
* Mark Wielaard (mjw at redhat.com) wrote:
> On Tue, 2011-04-12 at 14:48 -0400, Mathieu Desnoyers wrote:
> > * Frank Ch. Eigler (fche at redhat.com) wrote:
> > > How about just:
> > >
> > >
> > > #define SDT_USE_VARIADIC
> > > #include <sys/sdt.h>
> >
> > How should support systems that don't have sdt.h ? Is there a define we
> > could check ?
>
> I have just been using the following configure check:
>
> AC_CHECK_HEADER([sys/sdt.h], [SDT_H_FOUND='yes'],
> [SDT_H_FOUND='no';
> AC_MSG_ERROR([systemtap support needs sys/sdt.h header])])
>
> Which you can adapt to your needs with/without error message, including
> an test to see if it fully works for your environment.
Thanks for the hint, but adding this test in the UST build system don't
really make sense, because both systemtap and UST don't have dependency
on each other, and thus the build order between the two packages is not
fixed. So the detection should be done when the UST header is being
included into an application rather than at UST configuration time. And
I don't want to require all applications that want to use tracepoint to
use autoconf neither.
Mathieu
>
>
> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
>
--
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2011-04-13 15:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-10 17:44 Mathieu Desnoyers
2011-04-11 21:19 ` Josh Stone
2011-04-11 22:29 ` Josh Stone
2011-04-12 16:57 ` Frank Ch. Eigler
2011-04-12 18:35 ` Mathieu Desnoyers
2011-04-12 18:45 ` Frank Ch. Eigler
2011-04-12 18:48 ` Mathieu Desnoyers
2011-04-12 18:59 ` Frank Ch. Eigler
2011-04-12 19:12 ` Mark Wielaard
2011-04-13 15:38 ` Mathieu Desnoyers [this message]
[not found] ` <BLU0-SMTP42E61B0C2D4283651878B896AA0@phx.gbl>
2011-04-13 16:17 ` Mark Wielaard
2011-04-13 16:58 ` Mathieu Desnoyers
2011-04-13 17:24 ` Josh Stone
2011-04-13 17:29 ` Mark Wielaard
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=BLU0-SMTP6649154A1D0EEA973E63C396AA0@phx.gbl \
--to=compudj@krystal.dyndns.org \
/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