https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110017
--- Comment #1 from cqwrteur <unlvsur at live dot com> --- (In reply to cqwrteur from comment #0) > I attempted crossback compilation for GCC, where the compiler is built on > Linux, runs on Windows, and is targeted for Linux again. However, the build > system of libgcc includes a sanity test to detect the functionality of the > compiler, which prevents the build for the -mx32 option and disables m32. > > Moreover, during crossback compilation, GCC specifically looks for the "cc" > command instead of just "gcc," even in cases where it doesn't exist. > > Is there a way to remove or bypass the sanity test restriction for crossback > compilation in this scenario? Not the functionality. It detects whether -mx32 program could run but of course it cannot because linux kernel disabled that.
