From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH][gdb/build] Fix build with undefined CXX_STD_THREAD
Date: Wed, 8 Sep 2021 10:06:06 +0200 [thread overview]
Message-ID: <68b36a03-0d56-2e30-bc0e-403eda7b761c@suse.de> (raw)
In-Reply-To: <a30c92e2-cd35-8403-3382-d7dc32f90c8f@suse.de>
On 9/7/21 5:19 PM, Tom de Vries wrote:
> I find:
> ...
> CXX_DIALECT='-std=gnu++11'
> ...
> in the config.log, but that setting is not used when checking for
> CXX_STD_THREAD, so we have:
> ...
> configure:14614: checking for std::thread
> configure:14631: g++ -c -pthread -Wall -O2 -g conftest.cpp >&5
> In file included from /usr/include/c++/4.8/thread:35:0,
> from conftest.cpp:167:
> /usr/include/c++/4.8/bits/c++0x_warning.h:32:2: error: #error This file
> requires compiler and library support for the ISO C++ 2011 standard.
> This support is currently experimental, and must be enabled with the
> -std=c++11 or -std=gnu++11 compiler options.
> #error This file requires compiler and library support for the \
> ^
> conftest.cpp: In function 'int main()':
> conftest.cpp:172:1: error: 'thread' is not a member of 'std'
> std::thread t(callback);
> ^
> conftest.cpp:172:13: error: expected ';' before 't'
> std::thread t(callback);
> ^
> configure:14631: $? = 1
> ...
>
> It could be that:
> ...
> $ g++ -std=gnu++11 -c -pthread -Wall -O2 -g conftest.cpp
> ...
> actually would succeed.
Filed PR28318 - "[gdb/build] std::thread support configure check does
not use CXX_DIALECT" here (
https://sourceware.org/bugzilla/show_bug.cgi?id=28318 ).
Thanks,
- Tom
prev parent reply other threads:[~2021-09-08 8:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 14:50 Tom de Vries
2021-09-07 15:19 ` Tom de Vries
2021-09-07 16:12 ` Christian Biesinger
2021-09-08 7:02 ` Tom de Vries
2021-09-08 8:06 ` Tom de Vries [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=68b36a03-0d56-2e30-bc0e-403eda7b761c@suse.de \
--to=tdevries@suse.de \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).