Building a host-isolated gcc without faking cross-compiling

[Xi Ruoyao]

On Sat, 2021-09-11 at 04:55 +0000, Anthony de Almeida Lopes via Gcc-help
wrote:
> Alright, progress. I'm still researching the next problems that I ran
> into but I thought I'd post an update. First, I ran into
> GCC_NO_EXECUTABLES while the build was in configure-stage2-zlib and in
> anticipating what Lance might say to that, I checked and there doesn't
> seem to be a --without-zlib although I did test that just in case and
> it
> did nothing. The best explanation for what GCC_NO_EXECUTABLES is that
> I
> found so far is in a post to the list about a similar problem:
> 
> https://gcc.gnu.org/legacy-ml/gcc/2008-03/msg00515.html
> 
> I went ahead and built it anyway with --disable-bootstrap. glibc
> compiled but not too surprisingly running ldd or /usr/lib/libc.so.6
> with
> LD_LIBRARY_PATH to $DISTRO/usr/lib just segfaults, so it seems like it
> wasn't really a sane build of gcc after all.
> 
> Ignoring that problem, configuring libstdc++-v3 after having glibc
> fails
> which is kind of obvious since the host glibc differs in version from
> the target version. You know, the typical "version `GLIBC_2.34' not
> found" errors. This seems like a proper motivating reason for using
> the
> fake cross-compiling trick but I'm determined to figure out if there's
> a
> way around that.

As a LFS editor (and I also have several commits in GCC) I'd say there
is no rational way for this, expect cross-compilation.  Maybe you can
use a dozen of switches to accomplish the object, but at last it will be
almost equivelent to run a cross-compilation.
-- 
Xi Ruoyao <xry111@mengyan1223.wang>
School of Aerospace Science and Technology, Xidian University