This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/33200] install fails when trying to install fix-header since fix-header wasn't built
- From: "aldot at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 19 Jan 2008 14:14:42 -0000
- Subject: [Bug bootstrap/33200] install fails when trying to install fix-header since fix-header wasn't built
- References: <bug-33200-15021@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #5 from aldot at gcc dot gnu dot org 2008-01-19 14:14 -------
Assuming build=i386-linux-*, host==target==sh4-linux-*, i.e. cross-compiling a
native compiler for SuperH:
-) sh*-* forces use_fixproto in config.gcc (why?)
See config.gcc: line 2308
-) stmp-install-fixproto: fixproto
- The comment above this rule is wrong, fixproto is a shell-script.
- this rule doesn't depend on any fix-header, but the stamp is used
to unconditionally install fix-header.
-) build/fix-header${build_exeext}
Tries to compile a binary with mixed build- and host- objects, like
(abbreviated):
$HOSTCC -DGENERATOR_FILE -o build/fix-header \
build/fix-header.o c-incpath.o cppdefault.o build/scan-decls.o prefix.o \
build/scan.o build/errors.o ../libcpp/libcpp.a ../libiberty/libiberty etc.
where build/* is of course incompatible with the other object files.
This suggests that use_fixproto resp. stmp-install-fixproto makes only sense
for
host == build *or* (assuming this is not correct) that we need fix-header for
both build and for host (which is currently not implemented AFAICS).
Please advise.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33200