https://gcc.gnu.org/bugzilla/show_bug.cgi?id=123976
--- Comment #16 from Peter Dyballa <Peter_Dyballa at web dot de> ---
Even when Makefile has:
361 # Create links to files specified in config.host.
362 LIBGCC_LINKS = enable-execute-stack.c \
363 unwind.h md-unwind-def.h md-unwind-support.h \
364 sfp-machine.h gthr-default.h
365
366 enable-execute-stack.c: $(srcdir)/$(enable_execute_stack)
367 -$(LN_S) $< $@
368 sleep 2
369 unwind.h: $(srcdir)/$(unwind_header)
370 -$(LN_S) $< $@
371 sleep 2
372 md-unwind-def.h: $(srcdir)/config/$(md_unwind_def_header)
373 -$(LN_S) $< $@
374 sleep 2
375 md-unwind-support.h: $(srcdir)/config/$(md_unwind_header)
376 -$(LN_S) $< $@
377 sleep 2
378 sfp-machine.h: $(srcdir)/config/$(sfp_machine_header)
379 -$(LN_S) $< $@
380 sleep 2
381 gthr-default.h: $(srcdir)/$(thread_header)
382 -$(LN_S) $< $@
gmake makes only:
gmake[3]: Entering directory
'/opt/local/var/macports/build/gcc15-678e8911/work/build/powerpc-apple-darwin9/libgcc'
# If this is the top-level multilib, build all the other
# multilibs.
ln -s
/opt/local/var/macports/build/gcc15-678e8911/work/gcc-15.2.0/libgcc/gthr-posix.h
gthr-default.h
ln -s
/opt/local/var/macports/build/gcc15-678e8911/work/gcc-15.2.0/libgcc/config/no-unwind.h
md-unwind-support.h
sleep 2
ln -s
/opt/local/var/macports/build/gcc15-678e8911/work/gcc-15.2.0/libgcc/unwind-generic.h
unwind.h
sleep 2
DEFINES=''
HEADERS='/opt/local/var/macports/build/gcc15-678e8911/work/gcc-15.2.0/libgcc/config/i386/darwin-lib.h'
\
/opt/local/var/macports/build/gcc15-678e8911/work/gcc-15.2.0/libgcc/mkheader.sh
> tmp-libgcc_tm.h
/bin/sh
/opt/local/var/macports/build/gcc15-678e8911/work/gcc-15.2.0/libgcc/../move-if-change
tmp-libgcc_tm.h libgcc_tm.h
echo timestamp > libgcc_tm.stamp
/opt/local/var/macports/build/gcc15-678e8911/work/build/./gcc/xgcc -B ...
Three symlinks to C header file were created, two are missing, plus the symlink
to the C source file, enable-execute-stack.c. So half of the work seems to be
done – could the other half be done when I try to start the build process
again? NO!
But when I create the missing two symlinks to C header files and restart build,
then wondrously a symlink to the C source file is created:
Checking multilib configuration for libgcc...
gmake[3]: Entering directory
'/opt/local/var/macports/build/gcc15-678e8911/work/build/powerpc-apple-darwin9/libgcc'
# If this is the top-level multilib, build all the other
# multilibs.
/opt/local/var/macports/build/gcc15-678e8911/work/build/./gcc/xgcc -B... -c
/opt/local/var/macports/build/gcc15-678e8911/work/gcc-15.2.0/libgcc/unwind-dw2.c
/opt/local/var/macports/build/gcc15-678e8911/work/build/./gcc/xgcc -B... -c
/opt/local/var/macports/build/gcc15-678e8911/work/gcc-15.2.0/libgcc/config/unwind-dw2-fde-darwin.c
/opt/local/var/macports/build/gcc15-678e8911/work/build/./gcc/xgcc -B... -c
/opt/local/var/macports/build/gcc15-678e8911/work/gcc-15.2.0/libgcc/unwind-c.c
ln -s
/opt/local/var/macports/build/gcc15-678e8911/work/gcc-15.2.0/libgcc/enable-execute-stack-mprotect.c
enable-execute-stack.c
sleep 2
/opt/local/var/macports/build/gcc15-678e8911/work/build/./gcc/xgcc -B...
...
many, many xgcc invocations later
...
/opt/local/var/macports/build/gcc15-678e8911/work/build/./gcc/xgcc -B... -c
-xassembler-with-cpp
/opt/local/var/macports/build/gcc15-678e8911/work/gcc-15.2.0/libgcc/config/rs6000/darwin-tramp.S
/opt/local/var/macports/build/gcc15-678e8911/work/build/./gcc/xgcc -B... -c
/opt/local/var/macports/build/gcc15-678e8911/work/gcc-15.2.0/libgcc/config/darwin-64.c
/opt/local/var/macports/build/gcc15-678e8911/work/build/./gcc/xgcc -B... -c
/opt/local/var/macports/build/gcc15-678e8911/work/gcc-15.2.0/libgcc/config/rs6000/ibm-ldouble.c
/opt/local/var/macports/build/gcc15-678e8911/work/build/./gcc/xgcc -B... -c
enable-execute-stack.c
enable-execute-stack.c:33:13: warning: 'check_enabling' declared 'static' but
never defined [-Wunused-function]
33 | static void check_enabling (void) __attribute__ ((unused));
| ^~~~~~~~~~~~~~
/opt/local/var/macports/build/gcc15-678e8911/work/build/./gcc/xgcc -B...
There is one single dependency for six files (or symlinks) written down, but
some of these dependencies become obviously visible, or a problem/task to
resolve, only later. Could this be the actual cause?
The build process has entered the next stage. Next stop in one or two days?
