public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "qiyao at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug build/17104] CFLAGS="-Wall -Wextra" gdb/confgure --with-babeltrace fails Date: Tue, 01 Jul 2014 03:46:00 -0000 [thread overview] Message-ID: <bug-17104-4717-PQ435AcYBs@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-17104-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=17104 Yao Qi <qiyao at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |qiyao at gcc dot gnu.org --- Comment #1 from Yao Qi <qiyao at gcc dot gnu.org> --- I can reproduce it with gcc 4.8.2 (shipped on Fedora 20). configure:15245: gcc -o conftest -Wall -Wextra -Werror -I/home/yao/Source/lttng/babeltrace/1.1.0/install/include conftest.c -ldl -lncurses -lz -lm /home/yao/Source/lttng/babeltrace/1.1.0/install/lib/libbabeltrace.so /home/yao/Source/lttng/babeltrace/1.1.0/install/lib/libbabeltrace-ctf.so -lpopt -lgmodule-2.0 -lrt -lglib-2.0 -luuid -Wl,-rpath -Wl,/home/yao/Source/lttng/babeltrace/1.1.0/install/lib >&5 conftest.c: In function 'main': conftest.c:192:21: error: unused variable 'pos' [-Werror=unused-variable] struct bt_iter_pos *pos = bt_iter_get_pos (bt_ctf_get_iter (NULL)); ^ cc1: all warnings being treated as errors and this can be fixed by the following patch. However, I suspect whether GDB can be built with '-Wall -Wextra -Werror', because even with the patch, I still get build failure in libiberty and gdb later. 2014-07-01 Yao Qi <yao@codesourcery.com> build/17104 * configure.ac: Use local variable 'pos'. * configure: Regenerated. --- gdb/configure | 1 + gdb/configure.ac | 1 + 2 files changed, 2 insertions(+) diff --git a/gdb/configure b/gdb/configure index a4c0a8c..7956aa7 100755 --- a/gdb/configure +++ b/gdb/configure @@ -15234,6 +15234,7 @@ struct bt_iter_pos *pos = bt_iter_get_pos (bt_ctf_get_iter (NULL)); struct bt_ctf_event *event = NULL; const struct bt_definition *scope; + bt_iter_set_pos (bt_ctf_get_iter (NULL), pos); scope = bt_ctf_get_top_level_scope (event, BT_STREAM_EVENT_HEADER); bt_ctf_get_uint64 (bt_ctf_get_field (event, scope, "id")); diff --git a/gdb/configure.ac b/gdb/configure.ac index a2ac15f..fc1d8bc 100644 --- a/gdb/configure.ac +++ b/gdb/configure.ac @@ -2417,6 +2417,7 @@ else struct bt_ctf_event *event = NULL; const struct bt_definition *scope; + bt_iter_set_pos (bt_ctf_get_iter (NULL), pos); scope = bt_ctf_get_top_level_scope (event, BT_STREAM_EVENT_HEADER); bt_ctf_get_uint64 (bt_ctf_get_field (event, scope, "id")); -- 1.9.0 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-07-01 3:46 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-30 20:29 [Bug build/17104] New: " dilyan.palauzov at aegee dot org 2014-07-01 3:46 ` qiyao at gcc dot gnu.org [this message] 2014-08-12 19:23 ` [Bug build/17104] " jan.kratochvil at redhat dot com 2014-08-13 9:48 ` cvs-commit at gcc dot gnu.org 2014-08-13 9:52 ` cvs-commit at gcc dot gnu.org 2014-08-13 10:36 ` qiyao at gcc dot gnu.org
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=bug-17104-4717-PQ435AcYBs@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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).