Bug in make install-no-fixedincludes?
Nicolas Roche
roche@act-europe.fr
Tue Sep 2 09:00:00 GMT 2003
Hi,
I'm trying to build gcc and instead of making make install, I use :
make install-no-fixedincludes in order not to includes the fixed
includes.
the problem is that this lead to a recompilation of the gcclib and
then it fails because it can't find anymore the fixedincludes...
Indeed in the Makefile.in we have this:
gcc-no-fixedincludes:
@if [ -f ./gcc/Makefile ]; then \
rm -rf gcc/tmp-include; \
mv gcc/include gcc/tmp-include 2>/dev/null; \
mkdir gcc/include; \
cp $(srcdir)/gcc/gsyslimits.h gcc/include/syslimits.h; \
touch gcc/stmp-fixinc gcc/include/fixed; \
rm -f gcc/stmp-headers gcc/stmp-int-hdrs;
r=`${PWD_COMMAND}`; export r; \
s=`cd $(srcdir); ${PWD_COMMAND}` ; export s; \
$(SET_LIB_PATH) \
(cd ./gcc && \
$(MAKE) $(GCC_FLAGS_TO_PASS) install); \
rm -rf gcc/include; \
mv gcc/tmp-include gcc/include 2>/dev/null; \
else true; fi
stmp-int-hdrs is removed so that when you are calling the Makefile in
gcc subdir, the includes are reinstalled. As there is a touch of
stmp-fixinc, the fixedincludes are not regenerated. The problem is
that a new stmp-int-hdrs file is created and as it appears in
LIBGCC_DEPS, it leads to a recompilation of the libgcc.
So there is any workaround for this ? Is this a bug or not ?
Thanks in advance
Nicolas
More information about the Gcc-bugs
mailing list