From: Yao Qi <qiyaoltc@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Update gnulib to current upstream master
Date: Wed, 12 Oct 2016 16:09:00 -0000 [thread overview]
Message-ID: <CAH=s-PNP0csuzf_EH8m9kMfrxFuUb3JPiY4ZfvKgA_s9xFWdjQ@mail.gmail.com> (raw)
In-Reply-To: <1476285429-24489-1-git-send-email-palves@redhat.com>
On Wed, Oct 12, 2016 at 4:17 PM, Pedro Alves <palves@redhat.com> wrote:
> I tried building gdb with G++ 4.7 and CXX="g++ -std=gnu+11", and that
> tripped on a build error:
GDB source requires C++03 compiler, but it should be built with recent
compiler with recent C++ standard.
Patch is good to me, but let us leave this patch here for one day or two
for the purpose of collecting comments or objections.
--
Yao (齐尧)
next prev parent reply other threads:[~2016-10-12 16:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 15:17 Pedro Alves
2016-10-12 16:09 ` Yao Qi [this message]
2016-10-12 16:12 ` Pedro Alves
2016-10-12 16:23 ` Pedro Alves
2016-10-12 16:56 ` Eli Zaretskii
2016-10-12 17:10 ` Pedro Alves
2016-10-12 17:31 ` Eli Zaretskii
2016-10-12 16:30 ` Yao Qi
2016-10-18 22:20 ` [pushed] gdb: no longer define __STDC_CONSTANT_MACROS/__STDC_LIMIT_MACROS (Re: [PATCH] Update gnulib to current upstream master) Pedro Alves
2018-08-28 19:59 [PATCH] Update gnulib to current upstream master Sergio Durigan Junior
2018-08-29 16:19 ` Tom Tromey
2018-08-29 16:29 ` Sergio Durigan Junior
2018-08-29 19:06 ` Pedro Alves
2018-08-29 19:34 ` Sergio Durigan Junior
2018-08-31 13:04 ` Pedro Alves
2018-08-30 0:04 ` Tom Tromey
2018-08-30 3:01 ` Sergio Durigan Junior
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='CAH=s-PNP0csuzf_EH8m9kMfrxFuUb3JPiY4ZfvKgA_s9xFWdjQ@mail.gmail.com' \
--to=qiyaoltc@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