This is the mail archive of the
mailing list for the GCC project.
Re: gcc/f/malloc.h and HP-UX 10.20
- To: John David Anglin <dave at hiauly1 dot hia dot nrc dot ca>
- Subject: Re: gcc/f/malloc.h and HP-UX 10.20
- From: Toon Moene <toon at moene dot indiv dot nluug dot nl>
- Date: Fri, 25 May 2001 22:05:47 +0200
- CC: gcc at gcc dot gnu dot org, aoliva at redhat dot com, china at writtenword dot com, zackw at Stanford dot EDU
- Organization: Moene Computational Physics, Maartensdijk, The Netherlands
- References: <200105242359.TAA02914@hiauly1.hia.nrc.ca>
John David Anglin wrote:
> > Isn't that too subtle a fix? Even if the timestamps are updated,
> > building f/ansify.c with $(HOST_CC) is still wrong. So, you'd simply
> > be masking the problem.
> There isn't really a choice. You can't use the gcc target because it
> may not run on the host. The intdoc application has to run on
> the host and you need an ANSI compiler to build it. I have a patch
> that will allow building ansify with a non ANSI compiler but this
> is only the first step in generating the documentation. The situation
> really isn't much different than that for bison, autoconf, etc.
> Possibly, f/intdoc.texi should be in the list of files that contrib/gcc_update
Agreed. I managed to recreate the problem by touch'ing -t 1999090909
intdoc.texi and rerunning bootstrap.
intdoc.texi had a date of April 18th over here, because I had to
retrieve the entire tree afresh on that date.
intdoc.texi is a generated file and should be treated as such (i.e. the
person responsible for its update should check it in).
I'll keep that in mind next time intdoc.texi turns up M on my tree ...
Thanks (all) for the investigation !
Toon Moene - mailto:email@example.com - phoneto: +31 346 214290
Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
Maintainer, GNU Fortran 77: http://gcc.gnu.org/onlinedocs/g77_news.html
Join GNU Fortran 95: http://g95.sourceforge.net/ (under construction)