From: David Edelsohn <dje.gcc@gmail.com>
To: GDB Patches <gdb-patches@sourceware.org>,
Tom Tromey <tromey@redhat.com>, Pedro Alves <palves@redhat.com>
Subject: GDB AIX build broken
Date: Mon, 24 Oct 2016 22:40:00 -0000 [thread overview]
Message-ID: <CAGWvnyk1xaKTo7gMXPLjfg2QGYQteyp7qbXZ6C2_FdRpA09L1Q@mail.gmail.com> (raw)
GDB build on AIX is broken due to a recent commit.
g++ -g -O2 -I. -I/home/dje/src/binutils-gdb/gdb
-I/home/dje/src/binutils-gdb/gdb/common
-I/home/dje/src/binutils-gdb/gdb/config
-DLOCALEDIR="\"/usr/local/share/locale\"" -DHAVE_CONFIG_H
-I/home/dje/src/binutils-gdb/gdb/../include/opcode
-I/home/dje/src/binutils-gdb/gdb/../opcodes/..
-I/home/dje/src/binutils-gdb/gdb/../readline/..
-I/home/dje/src/binutils-gdb/gdb/../zlib -I../bfd
-I/home/dje/src/binutils-gdb/gdb/../bfd
-I/home/dje/src/binutils-gdb/gdb/../include -I../libdecnumber
-I/home/dje/src/binutils-gdb/gdb/../libdecnumber
-I/home/dje/src/binutils-gdb/gdb/gnulib/import -Ibuild-gnulib/import
-DTUI=1 -Wall -Wpointer-arith -Wno-unused -Wunused-value
-Wunused-function -Wno-switch -Wno-char-subscripts -Wempty-body
-Wunused-but-set-parameter -Wunused-but-set-variable -Wno-sign-compare
-Wno-write-strings -Wno-narrowing -Wformat-nonliteral -c -o buffer.o
-MT buffer.o -MMD -MP -MF .deps/buffer.Tpo
/home/dje/src/binutils-gdb/gdb/common/buffer.c
/home/dje/src/binutils-gdb/gdb/common/buffer.c: In function 'void
buffer_xml_printf(buffer*, const char*, ...)':
/home/dje/src/binutils-gdb/gdb/common/buffer.c:133:27: error: expected
')' before 'PRId64'
sprintf (str, "%" PRId64,
^~~~~~
/home/dje/src/binutils-gdb/gdb/common/buffer.c:134:43: warning:
spurious trailing '%' in format [-Wformat=]
(int64_t) va_arg (ap, long long));
^
/home/dje/src/binutils-gdb/gdb/common/buffer.c:134:43: warning: too
many arguments for format [-Wformat-extra-args]
/home/dje/src/binutils-gdb/gdb/common/buffer.c:137:27: error: expected
')' before 'PRIu64'
sprintf (str, "%" PRIu64,
^~~~~~
/home/dje/src/binutils-gdb/gdb/common/buffer.c:138:53: warning:
spurious trailing '%' in format [-Wformat=]
(uint64_t) va_arg (ap, unsigned long long));
^
/home/dje/src/binutils-gdb/gdb/common/buffer.c:138:53: warning: too
many arguments for format [-Wformat-extra-args]
/home/dje/src/binutils-gdb/gdb/common/buffer.c:141:27: error: expected
')' before 'PRIx64'
sprintf (str, "%" PRIx64,
^~~~~~
/home/dje/src/binutils-gdb/gdb/common/buffer.c:142:53: warning:
spurious trailing '%' in format [-Wformat=]
(uint64_t) va_arg (ap, unsigned long long));
^
/home/dje/src/binutils-gdb/gdb/common/buffer.c:142:53: warning: too
many arguments for format [-Wformat-extra-args]
/home/dje/src/binutils-gdb/gdb/common/buffer.c:145:27: error: expected
')' before 'PRIo64'
sprintf (str, "%" PRIo64,
^~~~~~
/home/dje/src/binutils-gdb/gdb/common/buffer.c:146:53: warning:
spurious trailing '%' in format [-Wformat=]
(uint64_t) va_arg (ap, unsigned long long));
^
/home/dje/src/binutils-gdb/gdb/common/buffer.c:146:53: warning: too
many arguments for format [-Wformat-extra-args]
Errors with PRIxxx macros normally mean a problem with header file
inclusion. for example, gdb/btrace.c, which also uses PRIxxx macros,
builds without error.
- David
next reply other threads:[~2016-10-24 22:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 22:40 David Edelsohn [this message]
2016-10-24 22:46 ` Pedro Alves
2016-10-24 22:53 ` David Edelsohn
2016-10-24 23:00 ` Pedro Alves
2016-10-25 0:13 ` David Edelsohn
2016-10-25 0:31 ` Pedro Alves
2016-10-25 0:50 ` Pedro Alves
2016-10-25 1:08 ` David Edelsohn
2016-10-25 1:22 ` Pedro Alves
2016-10-25 10:58 ` [pushed] Define __STDC_CONSTANT_MACROS/__STDC_LIMIT_MACROS again (Re: GDB AIX build broken) Pedro Alves
2016-10-25 12:41 ` David Edelsohn
2016-10-25 12:48 ` Pedro Alves
2016-10-25 12:54 ` [pushed] common/common-defs.h: Define __STDC_FORMAT_MACROS as well " Pedro Alves
2016-10-25 13:01 ` David Edelsohn
2016-10-25 0:51 ` GDB AIX build broken David Edelsohn
2016-10-25 1:10 ` Pedro Alves
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=CAGWvnyk1xaKTo7gMXPLjfg2QGYQteyp7qbXZ6C2_FdRpA09L1Q@mail.gmail.com \
--to=dje.gcc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=tromey@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