https://gcc.gnu.org/bugzilla/show_bug.cgi?id=126526
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The usual way people bootstrap is using boostrap-debug.mk and that builds
stage2 without debug info and stage3 with debug info, so a comparison problem
like that can't happen. I don't see --disable-bootstrap nor
--with-build-config= options used, so the only possibility why that wouldn't be
on (or unless using make profiledbootstrap -jN) is I think that toplevel
configure failed in
case $BUILD_CONFIG in
bootstrap-debug)
if echo "int f (void) { return 0; }" > conftest.c &&
${CC} -c conftest.c &&
mv conftest.o conftest.o.g0 &&
${CC} -c -g conftest.c &&
mv conftest.o conftest.o.g &&
${srcdir}/contrib/compare-debug conftest.o.g0 conftest.o.g > /dev/null
2>&1; then
:
else
BUILD_CONFIG=
fi
rm -f conftest.c conftest.o conftest.o.g0 conftest.o.g
;;
and selected an empty BUILD_CONFIG.
