This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
problem
- To: egcs at cygnus dot com
- Subject: problem
- From: mrs at wrs dot com (Mike Stump)
- Date: Thu, 30 Oct 1997 19:04:18 -0800
I was building egcs 971023 on HP 10.20, and found out that:
$(srcdir)/f/intdoc.texi: f/intdoc.c f/intdoc.in f/ansify.c f/intrin.def f/intrin.h
$(HOST_CC) $(HOST_CFLAGS) $(HOST_LDFLAGS) \
`echo $(srcdir)/f/ansify.c | sed 's,^\./,,'` -o f/ansify
requires that CC be an ANSI compiler, this didn't happen to be the
case with my /bin/cc.
Others will be likely to hit this.(?) If we are building a native
compiler, we should be able to use the compiler GCC_FOR_TARGET,
otherwise, short of recrafting the Fotran documentation, or
bootstrapping gcc for the native machine, I'm not sure how we fix it.
Ah, one other possibility comes to mind, if the docs are kinda static,
we can preprocess them and include the preprocessed version in the tar
file, so that you only wind up needing an ANSI compiler, if you modify
the docs.
I got around this by install -king the compiler, and reinstalling with
CC=gcc. That worked fine.