From: Pedro Alves <palves@redhat.com>
To: David Edelsohn <dje.gcc@gmail.com>,
GDB Patches <gdb-patches@sourceware.org>,
Tom Tromey <tom@tromey.com>
Subject: Re: GDB AIX build broken
Date: Mon, 24 Oct 2016 22:46:00 -0000 [thread overview]
Message-ID: <c3e19794-051a-70a9-3285-f991c0d88881@redhat.com> (raw)
In-Reply-To: <CAGWvnyk1xaKTo7gMXPLjfg2QGYQteyp7qbXZ6C2_FdRpA09L1Q@mail.gmail.com>
[fixed Tom's address]
On 10/24/2016 11:40 PM, David Edelsohn wrote:
> GDB build on AIX is broken due to a recent commit.
>
Which commit? Maybe the gnulib update? Is this a clean
build from scratch?
> /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,
> ^~~~~~
> 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.
Sounds like what you'd get if PRId64 is not defined in that
compilation unit, somehow.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-10-24 22:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 22:40 David Edelsohn
2016-10-24 22:46 ` Pedro Alves [this message]
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=c3e19794-051a-70a9-3285-f991c0d88881@redhat.com \
--to=palves@redhat.com \
--cc=dje.gcc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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