From: David Edelsohn <dje.gcc@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [pushed] common/common-defs.h: Define __STDC_FORMAT_MACROS as well (Re: GDB AIX build broken)
Date: Tue, 25 Oct 2016 13:01:00 -0000 [thread overview]
Message-ID: <CAGWvny=LK+RwD=tSdrzqrysxh6UbEa3OyJzyAN1obheOxpnSLQ@mail.gmail.com> (raw)
In-Reply-To: <9cb8f94e-7276-7351-081a-71640379dbc6@redhat.com>
On Tue, Oct 25, 2016 at 8:54 AM, Pedro Alves <palves@redhat.com> wrote:
> On 10/25/2016 01:48 PM, Pedro Alves wrote:
>> On 10/25/2016 01:41 PM, David Edelsohn wrote:
>
>>> Thanks, however...
>>>
>>> The missing macro is __STDC_FORMAT_MACROS. The macros that you
>>> re-added were not causing problems on AIX and don't enable the printf
>>> format macros in C++.
>>
>> Indeed, missed. Will add that too shortly.
>
> Done now. Let me know how it goes.
buffer.c now compiles.
Thanks, David
next prev parent reply other threads:[~2016-10-25 13:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 22:40 GDB AIX build broken David Edelsohn
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 [this message]
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='CAGWvny=LK+RwD=tSdrzqrysxh6UbEa3OyJzyAN1obheOxpnSLQ@mail.gmail.com' \
--to=dje.gcc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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).