This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: problem



> 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.

Sigh.

> 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'd like to avoid this if we can: we intentionally decided at the begining
to try to reduce bloat by not shipping .info files or old ChangeLogs.
We don't want to give that up too easily, I don't think.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]