testing consistency
Dave Love
d.love@dl.ac.uk
Fri Sep 19 14:51:00 GMT 1997
>>>>> "Joe" == Joe Buck <jbuck@synopsys.com> writes:
Joe> Another problem is that, the way the configure is done, it is
Joe> easy to wind up with bad data in the config.cache files for the
Joe> f77 runtime. The reason is that you wind up with something like
Joe> the following in gcc/f/runtime/config.cache (I've replaced the
Joe> directory containing the egcs distribution with <SRCDIR>).
Joe> ac_cv_prog_CC=${ac_cv_prog_CC='<SRCDIR>/gcc/xgcc -B<SRCDIR>/gcc/'}
The cache file has been taken out of the `clean' target for some
reason. It was there advisedly, normal GNU standards notwithstanding.
[This is one complication with using automake for the runtime.]
Joe> It would be more robust if we could avoid placing definitions of
Joe> ac_cv_prog_CC like this in the cache.
The idea was always to be sure the correct compiler was being used by
configure. I don't remember the cache file being a particular problem
during g77 development with the released GCCs (especially wrt bug
reports), though I've personally fallen over various things like this
occasionally :-/.
More information about the Gcc
mailing list