From: 何小乐 <hexiaole1994@126.com>
To: gcc-help@gcc.gnu.org
Subject: gcc7.3.0 link with -lstdc++fs but can not find
Date: Wed, 12 Jan 2022 12:34:39 +0800 (CST) [thread overview]
Message-ID: <5123161.1b55.17e4c9105aa.Coremail.hexiaole1994@126.com> (raw)
hello, friends, i compile cpp file using gcc7.3.0 with -lstdc++fs flags but the gcc complained, like below, i request for you help:
bash-5.0# c++ -o oomd oomd.p/src_oomd_Main.cpp.o -Wl,--as-needed -Wl,--no-undefined -Wl,--whole-archive -Wl,--start-group liboomd.a -Wl,--no-whole-archive -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/kylin/kylin-hardened-cc1 -fasynchronous-unwind-tables -fstack-clash-protection -Wl,-z,relro -Wl,-z,now -specs=/usr/lib/rpm/kylin/kylin-hardened-ld -lstdc++fs /usr/lib64/libjsoncpp.so -pthread /usr/lib64/libsystemd.so -Wl,--end-group
/usr/bin/ld: cannot find -lstdc++fs
collect2: error: ld returned 1 exit status
bash-5.0# c++ --version
c++ (GCC) 7.3.0
Copyright (C) 2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
bash-5.0# uname -a
Linux bogon 4.19.90-24.4.v2101.ky10.aarch64 #1 SMP Mon May 24 14:45:37 CST 2021 aarch64 aarch64 aarch64 GNU/Linux
and i confirm that this env has already installed the below rpm packages by yum tool:
gcc-c++.aarch64
libstdc++.aarch64
libstdc++-devel.aarch64
libstdc++-static.aarch64
and i failed to search for a keyword of 'stdc++fs' in my filesystem by find tool:
find / -name "*stdc++fs*"
i want to consult you how could i get the libstdc++fs*, thank you for your help!
next reply other threads:[~2022-01-12 4:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 4:34 何小乐 [this message]
2022-01-12 8:28 ` Xi Ruoyao
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=5123161.1b55.17e4c9105aa.Coremail.hexiaole1994@126.com \
--to=hexiaole1994@126.com \
--cc=gcc-help@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: 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).