public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: jistone@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.8-35-g037853b Date: Mon, 09 Jul 2012 19:22:00 -0000 [thread overview] Message-ID: <20120709192256.14383.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 037853b4644bb6ebd68e2f1fac11c3636f551d8e (commit) from 5aade0f939690a1839323f2dd14b6dd54735b25d (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 037853b4644bb6ebd68e2f1fac11c3636f551d8e Author: Josh Stone <jistone@redhat.com> Date: Mon Jul 9 12:07:48 2012 -0700 Fix the build with glibc 2.16 With our elevated compiler warnings as errors, we got: mainloop.c: In function 'stp_main_loop': mainloop.c:581:3: error: signed and unsigned type in conditional expression [-Werror=sign-compare] mainloop.c:581:3: error: signed and unsigned type in conditional expression [-Werror=sign-compare] mainloop.c:583:35: error: signed and unsigned type in conditional expression [-Werror=sign-compare] mainloop.c:583:35: error: signed and unsigned type in conditional expression [-Werror=sign-compare] mainloop.c:631:2: error: signed and unsigned type in conditional expression [-Werror=sign-compare] mainloop.c:631:2: error: signed and unsigned type in conditional expression [-Werror=sign-compare] cc1: all warnings being treated as errors This turns out to be a macro fight between glibc-2.16 and kernel-headers, via including linux/types.h. We apparently don't even need that header, so removing it lets us proceed normally. Those curious can watch this bug to see how the conflict is resolved: https://bugzilla.redhat.com/show_bug.cgi?id=837641 ----------------------------------------------------------------------- Summary of changes: staprun/staprun.h | 1 - 1 files changed, 0 insertions(+), 1 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2012-07-09 19:22 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=20120709192256.14383.qmail@sourceware.org \ --to=jistone@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).