I guess I'm doing something wrong, or not enough. "make install" is
failing after a bootstrap build because the build/fixincludes directory
is empty. Edited for brevity:
$ make -C build-boot/ V=1 install
make: Entering directory '.../build-boot'
make[1]: Entering directory '.../build-boot'
/bin/bash ../mkinstalldirs /usr/local/gcc-cobol /usr/local/gcc-cobol
make[2]: Entering directory '.../build-boot/fixincludes'
make[2]: *** No rule to make target 'install'. Stop.
make[2]: Leaving directory '.../build-boot/fixincludes'
make[1]: *** [Makefile:4193: install-fixincludes] Error 2
make[1]: Leaving directory '.../build-boot'
make: *** [Makefile:2710: install] Error 2
make: Leaving directory '.../build-boot'
$ for D in build*/fixincludes
do
printf "$D: %d files\n" $(ls $D | wc -l)
done
build-02/fixincludes: 18 files
build-boot/fixincludes: 0 files
build/fixincludes: 18 files
Until recently I always used --disable-bootstrap because faster.
Lately because of the discomfort of my own petard I have added
--enable-bootstrap to my repertoire. The build succeeds, but leaves
the fixincludes directory empty, which means "make install" fails. I
thought the issue was confined to building on macOS, but today discover
it's true (as above) on Ubuntu x86_64.
The configure invocation is nothing special:
$ head build-boot/config.log | grep /configure
$ ../configure --prefix=/usr/local/gcc-cobol
--disable-generated-files-in-srcdir --disable-multilib
--enable-checking --enable-languages=c,cobol
These are branches based on master, updated as of yesterday. (I have
other examples without --disable-generated-files-in-srcdir.)
A comparison of the mentions of "fixinclude" in config.{status,log} of
two directories, bootstrap and non-bootstrap, shows no difference.
What should I be looking for?
--jkl
