https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103528
--- Comment #5 from Iain Buclaw <ibuclaw at gdcproject dot org> --- (In reply to Rainer Orth from comment #0) > * toplevel configure needs to make certain that the bootstrap gdc can compile > *and link* some trivial D program. Letting the build proceed otherwise > leads > to confusing link errors as seen here. gnat can do away without such a > test > because there are no gnat without libgnat configurations (either you have a > fully working GNAT or you have none), while the gdc without libphobos > situation is quite common in GCC. I'm on the side-line with that observation though, gdc without libphobos has been defaulted in configure.tgt more because I lack the means for testing such a broad amount of targets (such as non-x86 BSDs). When someone does test it (powerpc64le-freebsd) the report I get back is usually that it works fine. Rather gdc without libphobos is more of an exception, because the compiler heavily depends on it existing anyway, with many high-level features lowered into calls of core druntime helper functions. Without a runtime, this severely limits what you can do in the language to a strict subset (that might as well be C). To pick a similar example, is this a bug? Or can it be explained away with documentation? --- checking for long long... yes checking size of long long... configure: error: in `/work/gcc/build/gcc': configure: error: cannot compute sizeof (long long) See `config.log' for more details make[1]: *** [Makefile:4511: configure-gcc] Error 1 make[1]: Leaving directory '/work/gcc/build' make: *** [Makefile:985: all] Error 2 --- (config.log) configure:6450: checking size of long long configure:6455: g++ -o conftest -g conftest.cpp >&5 /usr/bin/ld: cannot find -lstdc++ collect2: error: ld returned 1 exit status configure:6455: $? = 1 configure: program exited with status 1 ---
