From: "ankita at in dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug tapsets/9899] New: Systemtap source compilation failure on latest Ubuntu
Date: Wed, 25 Feb 2009 10:28:00 -0000 [thread overview]
Message-ID: <20090225101253.9899.ankita@in.ibm.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]
When compiling the latest systemtap tarball, v 0;9 with 0.140 elfutils package,
gives the following compile time warning:
tapsets.cxx: In member function ‘std::string
dwflpp::express_as_string(std::string, std::string, location*)’:
tapsets.cxx:2299: error: format not a string literal and no format arguments
tapsets.cxx:2301: error: format not a string literal and no format arguments
Since the Makefile passes the -Werror flag, warnings are treated as errors and
the compilation aborts.
This was seen on a x86_64 system on Ubuntu Intrepid (8.10), running 2.6.29-rc4
kernel, with gcc version 4.3.2.
--
Summary: Systemtap source compilation failure on latest Ubuntu
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: tapsets
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: ankita at in dot ibm dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=9899
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2009-02-25 10:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 10:28 ankita at in dot ibm dot com [this message]
2009-02-25 11:35 ` [Bug tapsets/9899] " ankita at in dot ibm dot com
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=20090225101253.9899.ankita@in.ibm.com \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.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 read-only IMAP folder(s) and NNTP newsgroup(s).