public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/108636] C++20 undefined reference to `std::filesystem::__cxx11::path::_List::type(std::filesystem::__cxx11::path::_Type)' with -fkeep-inline-functions Date: Thu, 02 Feb 2023 13:25:59 +0000 [thread overview] Message-ID: <bug-108636-4-5eSFDiox8e@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108636-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108636 --- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> --- Trunk has some additional errors: /usr/bin/ld: /tmp/ccXeUWH9.o: in function `std::filesystem::__cxx11::directory_iterator::operator==(std::default_sentinel_t) const': /home/jwakely/src/gcc/build/x86_64-pc-linux-gnu/libstdc++-v3/include/bits/fs_dir.h:436: undefined reference to `std::__shared_ptr<std::filesystem::__cxx11::_Dir, (__gnu_cxx::_Lock_policy)2>::operator bool() const' /usr/bin/ld: /tmp/ccXeUWH9.o: in function `std::filesystem::__cxx11::recursive_directory_iterator::operator==(std::default_sentinel_t) const': /home/jwakely/src/gcc/build/x86_64-pc-linux-gnu/libstdc++-v3/include/bits/fs_dir.h:544: undefined reference to `std::__shared_ptr<std::filesystem::__cxx11::recursive_directory_iterator::_Dir_stack, (__gnu_cxx::_Lock_policy)2>::operator bool() const' I think the answer is "don't use -fkeep-inline-functions"
next prev parent reply other threads:[~2023-02-02 13:25 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-02 12:03 [Bug c++/108636] New: C++20 to " hnc at singularity dot fr 2023-02-02 12:11 ` [Bug libstdc++/108636] " redi at gcc dot gnu.org 2023-02-02 13:25 ` redi at gcc dot gnu.org [this message] 2023-02-02 13:46 ` [Bug libstdc++/108636] C++20 " redi at gcc dot gnu.org 2023-02-02 16:47 ` cvs-commit at gcc dot gnu.org 2023-02-02 17:12 ` [Bug libstdc++/108636] [10/11/12 Regression] " redi at gcc dot gnu.org 2023-02-21 0:48 ` cvs-commit at gcc dot gnu.org 2023-03-16 16:51 ` [Bug libstdc++/108636] [10/11 " cvs-commit at gcc dot gnu.org 2023-03-16 17:53 ` [Bug libstdc++/108636] [10 " cvs-commit at gcc dot gnu.org 2023-03-16 17:54 ` redi at gcc dot gnu.org 2024-01-31 22:23 ` Mark_B53 at yahoo dot com 2024-02-01 18:36 ` redi at gcc dot gnu.org 2024-02-02 10:35 ` cvs-commit at gcc dot gnu.org 2024-02-02 10:40 ` redi 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-108636-4-5eSFDiox8e@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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).