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++/100057] There are no freestanding C++ Date: Thu, 30 Dec 2021 10:25:20 +0000 [thread overview] Message-ID: <bug-100057-4-XMbeERtX7H@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100057-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100057 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|WAITING |RESOLVED --- Comment #38 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Nicolas Noble from comment #33) > At the moment, I don't understand if it's possible to spawn a cross compiler > with a freestanding libc and libstdc++. A GCC bootstrap needs a hosted libstdc++, because it's built with C++. If you want to disable hosted libstdc++ you need to also build with --disable-bootstrap. (In reply to Nicolas Noble from comment #34) > After some digging, I found out this in the acinclude.m4 file of the > libstdc++-v3 folder: > > AC_DEFUN([GLIBCXX_ENABLE_HOSTED], [ > AC_ARG_ENABLE([hosted-libstdcxx], > AC_HELP_STRING([--disable-hosted-libstdcxx], > [only build freestanding C++ runtime support]),, > [case "$host" in > arm*-*-symbianelf*) > enable_hosted_libstdcxx=no > ;; > *) > enable_hosted_libstdcxx=yes > ;; > esac]) > > > Basically, it looks like the "disable hosted libstdc++" flag is only honored > when building on a host triple that's arm + symbian. No, that code snippet is the action-if-not-given clause, which means it runs if you do not use --disable-hosted-libstdcxx or --enable-hosted-libstdcxx, i.e. the default for symbian is freestanding, the default for other systems is hosted. But you can override the default. > The documentation + > reporting for this is extremely misguiding. The documentation should at > least specify this only works in a very narrow context, and the configure > script should probably error out if the user asks for a feature it can't > actually provide. No, the docs don't say that because it's not true, you've just completely misunderstood the configure script. I'm closing this bug, because "cqwrteur" is a moron who can't report useful bugs. If you need help building freestanding please use the gcc-help mailing list, or the libstdc++ list, or open a new bug. Stay away from everything cqwrteur reports, because it's toxic garbage and I'm not interested in dealing with his nonsense.
next prev parent reply other threads:[~2021-12-30 10:25 UTC|newest] Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-13 0:22 [Bug libstdc++/100057] New: " unlvsur at live dot com 2021-04-13 0:26 ` [Bug libstdc++/100057] " unlvsur at live dot com 2021-04-13 0:29 ` unlvsur at live dot com 2021-04-13 0:44 ` unlvsur at live dot com 2021-04-13 0:58 ` unlvsur at live dot com 2021-04-13 1:34 ` phdofthehouse at gmail dot com 2021-04-13 1:36 ` phdofthehouse at gmail dot com 2021-04-13 1:53 ` unlvsur at live dot com 2021-04-13 1:57 ` unlvsur at live dot com 2021-04-13 2:20 ` unlvsur at live dot com 2021-04-13 2:21 ` unlvsur at live dot com 2021-04-13 2:49 ` unlvsur at live dot com 2021-04-13 3:58 ` unlvsur at live dot com 2021-04-13 4:36 ` unlvsur at live dot com 2021-04-13 5:12 ` unlvsur at live dot com 2021-04-13 7:50 ` unlvsur at live dot com 2021-04-13 8:12 ` unlvsur at live dot com 2021-04-13 8:14 ` unlvsur at live dot com 2021-04-13 8:46 ` rguenth at gcc dot gnu.org 2021-04-13 8:48 ` unlvsur at live dot com 2021-04-13 8:51 ` unlvsur at live dot com 2021-04-13 8:57 ` rguenth at gcc dot gnu.org 2021-04-13 9:06 ` unlvsur at live dot com 2021-04-13 9:24 ` redi at gcc dot gnu.org 2021-04-13 9:27 ` redi at gcc dot gnu.org 2021-04-13 9:41 ` redi at gcc dot gnu.org 2021-04-13 10:01 ` unlvsur at live dot com 2021-04-13 10:32 ` unlvsur at live dot com 2021-04-13 10:50 ` redi at gcc dot gnu.org 2021-08-21 8:50 ` unlvsur at live dot com 2021-08-23 10:08 ` redi at gcc dot gnu.org 2021-08-23 10:16 ` unlvsur at live dot com 2021-08-23 10:19 ` unlvsur at live dot com 2021-12-29 22:17 ` pixel@nobis-crew.org 2021-12-29 23:04 ` pixel@nobis-crew.org 2021-12-29 23:57 ` unlvsur at live dot com 2021-12-29 23:57 ` unlvsur at live dot com 2021-12-30 10:19 ` redi at gcc dot gnu.org 2021-12-30 10:25 ` redi at gcc dot gnu.org [this message] 2021-12-30 10:56 ` redi at gcc dot gnu.org 2021-12-30 11:31 ` redi at gcc dot gnu.org 2021-12-30 18:37 ` unlvsur at live dot com 2021-12-30 18:39 ` unlvsur at live dot com
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-100057-4-XMbeERtX7H@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).