From: Jakub Jelinek <jakub@redhat.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: libc-alpha@sourceware.org, gcc@gcc.gnu.org
Subject: Re: Failures building glibc with mainline GCC
Date: Fri, 30 Jul 2021 18:43:15 +0200 [thread overview]
Message-ID: <20210730164315.GO2380545@tucnak> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2107301637590.581212@digraph.polyomino.org.uk>
On Fri, Jul 30, 2021 at 04:38:58PM +0000, Joseph Myers wrote:
> In addition to failures building glibc, for those configurations for which
> glibc builds there's a failure building the testsuite:
>
> tst-thread_local1.cc:177:5: error: variable 'std::array<std::pair<const char*, std::function<void(void* (*)(void*))> >, 2> do_thread_X' has initializer but incomplete type
> 177 | do_thread_X
> | ^~~~~~~~~~~
This is likely a test bug, Jonathan has changed the libstdc++ headers like
many times already to include fewer includes for the internal implementation
details when the standard doesn't require everything or specific parts from
one header to appear whenever including another one.
Usually one needs to add new includes when this happens for whatever the
test is using.
Jakub
next prev parent reply other threads:[~2021-07-30 16:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 15:30 Joseph Myers
2021-07-30 16:19 ` Aldy Hernandez
2021-07-30 16:22 ` Jeff Law
2021-07-30 16:45 ` Jeff Law
2021-07-30 17:28 ` Martin Sebor
2021-07-30 20:52 ` Joseph Myers
2021-08-02 20:20 ` Martin Sebor
2021-08-03 15:54 ` Joseph Myers
2021-08-03 16:20 ` Martin Sebor
2021-08-03 17:21 ` Joseph Myers
2021-08-03 17:39 ` Samuel Thibault
2021-08-03 22:33 ` Martin Sebor
2021-08-03 20:50 ` Segher Boessenkool
2021-08-03 21:00 ` Joseph Myers
2021-08-03 22:02 ` Segher Boessenkool
2021-08-03 22:59 ` Martin Sebor
2021-07-30 16:38 ` Joseph Myers
2021-07-30 16:43 ` Jakub Jelinek [this message]
2021-07-30 16:53 ` Martin Sebor
2021-07-30 17:02 ` Jakub Jelinek
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=20210730164315.GO2380545@tucnak \
--to=jakub@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@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).