From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: unlvsur unlvsur <unlvsur@live.com>
Cc: "unlvsur unlvsur via Libstdc++" <libstdc++@gcc.gnu.org>
Subject: Re: Is that possible to build libstdc++ without std::filesystem?
Date: Fri, 15 Oct 2021 01:16:53 +0100 [thread overview]
Message-ID: <CAH6eHdQGNqU8oGCuKknEZp6swEyj9coaKkK7UQTD3O3WfvG1QA@mail.gmail.com> (raw)
In-Reply-To: <DM6PR05MB4697CFCF81C46AF74131D86CD6B89@DM6PR05MB4697.namprd05.prod.outlook.com>
On Thu, 14 Oct 2021, 23:50 unlvsur unlvsur via Libstdc++, <
libstdc++@gcc.gnu.org> wrote:
> I have some platforms where I do not have correct filesystem support. I
> want to disable them to prevent dynamic linking errors.
>
You would have to edit the makefiles, there is no configure option to do it.
As the name suggests, --disable-libstdcxx-filesystem-ts only affects the TS
symbols, by preventing libstdc++fs.a from being built. It doesn't affect
the std:: filesystem symbols in libstdc++.so
prev parent reply other threads:[~2021-10-15 0:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 22:49 unlvsur unlvsur
2021-10-15 0:16 ` Jonathan Wakely [this message]
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=CAH6eHdQGNqU8oGCuKknEZp6swEyj9coaKkK7UQTD3O3WfvG1QA@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=libstdc++@gcc.gnu.org \
--cc=unlvsur@live.com \
/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).