public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Fangrui Song <maskray@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc/google/grte/v5-2.27/master] Fix build of nptl/tst-thread_local1.cc with GCC 12 Date: Thu, 27 Oct 2022 20:50:08 +0000 (GMT) [thread overview] Message-ID: <20221027205008.58FBC3887F57@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=7255e947f2ee7700d0a2f4115f9598e2dd8f3c2c commit 7255e947f2ee7700d0a2f4115f9598e2dd8f3c2c Author: Joseph Myers <joseph@codesourcery.com> Date: Mon Aug 2 16:33:44 2021 +0000 Fix build of nptl/tst-thread_local1.cc with GCC 12 The test nptl/tst-thread_local1.cc fails to build with GCC mainline because of changes to what libstdc++ headers implicitly include what other headers: tst-thread_local1.cc: In function 'int do_test()': 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 | ^~~~~~~~~~~ Fix this by adding an explicit include of <array>. Tested with build-many-glibcs.py for aarch64-linux-gnu. (cherry picked from commit 2ee9b24f47db8d0a8d0ccadb999335a1d4cfc364) Diff: --- nptl/tst-thread_local1.cc | 1 + 1 file changed, 1 insertion(+) diff --git a/nptl/tst-thread_local1.cc b/nptl/tst-thread_local1.cc index 0cfdcd6d19..5f4cf5cc3b 100644 --- a/nptl/tst-thread_local1.cc +++ b/nptl/tst-thread_local1.cc @@ -21,6 +21,7 @@ #include <stdio.h> #include <string.h> +#include <array> #include <functional> #include <string> #include <thread>
reply other threads:[~2022-10-27 20:50 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221027205008.58FBC3887F57@sourceware.org \ --to=maskray@sourceware.org \ --cc=glibc-cvs@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: linkBe 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).