public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/28318] [gdb/build] std::thread support configure check does not use CXX_DIALECT
Date: Wed, 08 Sep 2021 08:48:38 +0000 [thread overview]
Message-ID: <bug-28318-4717-8hammw8MA1@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28318-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28318
--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
Created attachment 13657
--> https://sourceware.org/bugzilla/attachment.cgi?id=13657&action=edit
[gdb/build] Add CXX_DIALECT to CXX
(In reply to Tom de Vries from comment #1)
> - we add CXX_DIALECT to CXX directly. AFAIU, that wouldn't break anything
> though it would result in confusing double options in command lines.
Patch implementing this.
Indeed now we have:
...
configure:8916: checking for std::thread
configure:8933: g++ -std=gnu++11 -c -pthread -Wall -O2 -g conftest.cpp >&5
configure:8933: $? = 0
configure:8940: result: yes
...
but indeed in the build/gdb/Makefile:
...
CXX = g++ -std=gnu++11
CXX_DIALECT = -std=gnu++11
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-09-08 8:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 7:49 [Bug build/28318] New: [gdb/build] std::thread support configure check does not used CXX_DIALECT vries at gcc dot gnu.org
2021-09-08 8:04 ` [Bug build/28318] [gdb/build] std::thread support configure check does not use CXX_DIALECT vries at gcc dot gnu.org
2021-09-08 8:48 ` vries at gcc dot gnu.org [this message]
2021-09-08 8:51 ` vries at gcc dot gnu.org
2021-09-08 12:16 ` vries at gcc dot gnu.org
2021-10-04 16:56 ` cvs-commit at gcc dot gnu.org
2021-10-04 16:58 ` vries at gcc dot gnu.org
2021-10-04 18:31 ` brobecker at gnat dot com
2021-10-04 18:58 ` vries at gcc dot gnu.org
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=bug-28318-4717-8hammw8MA1@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.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).