https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104006
--- Comment #22 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> --- > --- Comment #21 from Jakub Jelinek <jakub at gcc dot gnu.org> --- > That is make -j48 from where? > Toplevel, or the libgfortran build dir, or toplevel make -j48 > all-target-libgfortran or make -j48 maybe-all-target-libgfortran? Both make -j48 from toplevel (within a regular bootstrap) and make -j48 all from libgfortran build dir. > From what I can see, toplevel all-target-libgfortran should do make all in the > libgfortran build dir: [...] > and all: in the libgfortran Makefile should be: > all: $(BUILT_SOURCES) config.h > $(MAKE) $(AM_MAKEFLAGS) all-am > (in your case with the ls -l added above it). Right. > Perhaps also above the ls do > echo all in libgfortran, BUILT_SOURCES is $(BUILT_SOUCES) No difference: that output doesn't show up in the log. > What version of GNU make are you using? Usually, it's 4.2.92 in an attempt to avoid make SEGVs I sometimes observed on Solaris 10. However, I tried the same with 4.2.1: same result. > I just don't understand how it could start building the object files etc. > which is done from all-am before actually ensuring all those $(BUILT_SOURCES) > like kinds.h exist. I've attached the log. The first one it builds (after creating selected_int_kind.inc, selected_real_kind.inc, kinds.h, c99_protos.h, fpu-target.h, and ISO_Fortran_binding.h) is bounds.lo.