[Bug libstdc++/103866] AM_PROG_LIBTOOL not compatible with GCC_NO_EXECUTABLES

[redi at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103866

--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
More generally, it would be good if --with-newlib wasn't needed as a kluge to
mean "no libc" as well as "libc is newlib". It's surprising to users that
--without-headers doesn't mean "no libc", but --with-newlib does (when the
obvious expectation is that --with-newlib means you're using newlib as libc!)

Maybe --disable-hosted-libstdcxx should imply --with-newlib and
--disable-dlopen and whatever other options are needed to do this properly, so
you don't need to know the right undocumented combination.