public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "kadler at us dot ibm.com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/27123] Build fails for AIX 6.1
Date: Fri, 05 Aug 2022 21:44:58 +0000	[thread overview]
Message-ID: <bug-27123-4717-9Q7cJCGT40@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27123-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=27123

Kevin Adler <kadler at us dot ibm.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kadler at us dot ibm.com

--- Comment #2 from Kevin Adler <kadler at us dot ibm.com> ---
GCC has separate ABIs on AIX: threaded and non-threaded. Without the -pthread
flag, GCC will use the non-threaded ABI which does not define thread-related
C++ classes. These definitions are guarded by #ifdef _GLIBCXX_HAS_GTHREADS
which is set in one of:
- include/c++/.../bits/c++config.h
- include/c++/.../ppc64/bits/c++config.h
- include/c++/.../pthread/bits/c++config.h
- include/c++/.../pthread/ppc64/bits/c++config.h

depending on which -maix32/-maix64 and -pthread parameters (if any) were
passed. (Note that GCC 10, IIRC, changed the above layout to
ppc{32,64}/{pthread,} instead.)


If the build rule for thread-pool.cc is not passing the -pthread option, these
sorts of compilation errors will occur. The "make V=1" output would be helpful
to diagnose the problem further or see if the rule uses PTHREAD_CFLAGS.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-08-05 21:44 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
2022-02-27 23:17 ` tromey at sourceware dot org
2022-08-05 21:44 ` kadler at us dot ibm.com [this message]
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-9Q7cJCGT40@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).