public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/27123] Build fails for AIX 6.1
Date: Sun, 27 Feb 2022 23:17:44 +0000 [thread overview]
Message-ID: <bug-27123-4717-tLbIexaZRX@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27123-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27123
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
> Yet these are reported as not being included by gcc.
Offhand I don't know why this might be happening.
configure thinks std::thread works:
configure:9690: checking for std::thread
configure:9707: /opt/freeware/gcc-10.2.0/bin/g++-10 -c -pthread -O3
-mcpu=powerpc -std=c++17
-I/opt/freeware/gcc-10.2.0/lib/gcc/powerpc-ibm-aix6.1.9.0/10/include
conftest.cpp >&5
configure:9707: $? = 0
One thing you can do is try examining the full compilation command with
"make V=1".
Also it sometimes helps if you paste the entire command and output here.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-02-27 23:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 17:53 [Bug build/27123] New: Build fails for AIX 6.` parkej88 at gmail dot com
2020-12-28 17:55 ` [Bug build/27123] Build fails for AIX 6.1 parkej88 at gmail dot com
2022-02-27 23:17 ` tromey at sourceware dot org [this message]
2022-02-27 23:17 ` tromey at sourceware dot org
2022-08-05 21:44 ` kadler at us dot ibm.com
2022-08-07 12:05 ` parkej88 at gmail dot com
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-27123-4717-tLbIexaZRX@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).