From: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>
To: Vaseeharan Vinayagamoorthy <Vaseeharan.Vinayagamoorthy@arm.com>,
Szabolcs Nagy <Szabolcs.Nagy@arm.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] configure: Require C++11 for building code generation tools
Date: Thu, 20 Aug 2020 18:43:58 +0100 [thread overview]
Message-ID: <d83aa0e4-24d5-0133-88ed-b300c03acdb9@arm.com> (raw)
In-Reply-To: <37ECA5CF-D9F4-4C74-A7BB-5668883CC1F2@arm.com>
On 20/08/2020 18:07, Vaseeharan Vinayagamoorthy wrote:
> Hi Szabolcs,
>
> In the top level gcc config.log, I see:
>
> configure:5541: checking whether aarch64-none-linux-gnu-g++ supports C++11 features by default
> configure:5837: aarch64-none-linux-gnu-g++ -c -g -O2 conftest.cpp >&5
> configure:5837: $? = 0
> configure:5844: result: yes
> configure:6542: checking whether g++ supports C++11 features by default
> configure:6845: result: yes
>
> Not sure whether that helps?
>
I suspect this is a host/build confusion issue. Are you sure that's the
compiler used for BUILD?
R.
> Regards
> Vasee
>
>
> On 20/08/2020, 16:26, "Szabolcs Nagy" <Szabolcs.Nagy@arm.com> wrote:
>
> The 08/20/2020 13:59, Vasee Vinayagamoorthy wrote:
> > +# Also require C++11 for building code generation tools.
> > +# Do nothing if "${build}" = "${host}", because in this case
> > +# CXX_FOR_BUILD="\$(CXX)", and $CXX is already set to the correct value above.
> > +if test "${build}" != "${host}"; then
> > + saved_CXX=$CXX
> > + saved_CXXCPP=$CXXCPP
> > + CXX=$CXX_FOR_BUILD
> > + CXXCPP=
> > + AX_CXX_COMPILE_STDCXX(11)
> > + CXX="$CXX -std=c++11"
> > + CXX_FOR_BUILD=$CXX
> > + CXX=$saved_CXX
> > + CXXCPP=$saved_CXXCPP
> > +fi
>
> i think AX_CXX_COMPILE_STDCXX(11) should
> set CXX correctly (it seems it would set
> it to "g++ -std=gnu++11" instead of
> "g++ -std=c++11" but either should work)
>
> please look at the top level config.log
> i think you should look for
>
> "checking whether g++ supports C++11 features with -std=gnu++11"
>
> and that check should be successful.
>
prev parent reply other threads:[~2020-08-20 17:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-20 12:59 Vasee Vinayagamoorthy
2020-08-20 14:19 ` Ilya Leoshkevich
2020-08-20 16:29 ` Tobias Burnus
2020-08-20 20:40 ` Vaseeharan Vinayagamoorthy
2020-08-20 15:25 ` Szabolcs Nagy
2020-08-20 17:07 ` Vaseeharan Vinayagamoorthy
2020-08-20 17:43 ` Richard Earnshaw (lists) [this message]
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=d83aa0e4-24d5-0133-88ed-b300c03acdb9@arm.com \
--to=richard.earnshaw@arm.com \
--cc=Szabolcs.Nagy@arm.com \
--cc=Vaseeharan.Vinayagamoorthy@arm.com \
--cc=gcc-patches@gcc.gnu.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: 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).