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.
