public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: scox@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.2-245-g278c975 Date: Thu, 10 Jun 2010 21:42:00 -0000 [thread overview] Message-ID: <20100610214207.25062.qmail@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "systemtap: system-wide probe/trace tool". The branch, master has been updated via 278c9759d4957059a502decbb9a06c4026312b4c (commit) from f8edd50a6ba8cc81585bb36df074817e77259dda (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 278c9759d4957059a502decbb9a06c4026312b4c Author: Stan Cox <scox@redhat.com> Date: Thu Jun 10 17:40:29 2010 -0400 Fix tests for -DSTAP_SDT_V2. dtrace -G -s foo.d builds foo.o so it must pass -DSTAP_SDT_V2 to gcc. Add a -D flag (sun dtrace also has a -D flag) and pass that to the gcc invocation. * dtrace.in (semaphore_def_append): Make -DSTAP_SDT_V1 the default. (generate): Likewise. (main): Add -D and pass to cpp and gcc. * sdt_misc.exp: Run dtrace every iteration and pass it -DSTAP_SDT_V2. ----------------------------------------------------------------------- Summary of changes: dtrace.in | 19 +++++++----- testsuite/systemtap.base/sdt_misc.exp | 47 ++++++++++++++++++-------------- 2 files changed, 37 insertions(+), 29 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-06-10 21:42 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100610214207.25062.qmail@sourceware.org \ --to=scox@sourceware.org \ --cc=systemtap-cvs@sourceware.org \ --cc=systemtap@sourceware.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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).