http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46720
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |burnus at gcc dot gnu.org
Severity|enhancement |normal
--- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> 2010-12-02
10:33:00 UTC ---
(In reply to comment #1)
> The issue seems to be fixed after upgrading to automake 1.11.1
> from 1.11, so I am ready to resolve this as invalid.
1.11.1 is the correct version according to
http://gcc.gnu.org/install/prerequisites.html ("GCC requires the latest release
in the 1.11 series, which is currently 1.11.1.")
> However, two points:
> - The build process complains about the automake 1.11, but this warning
> scrolls past really fast, and if automake 1.11 really causes issues,
> this should be addressed.
No idea about that one. Except: "When regenerating a directory to a newer
version, please update all the directories using an older 1.11 to the latest
released version."
> - The timestamps on the generated files should be set so that no
> unneeded regeneration takes place.
No idea. Except using ./contrib/gcc_update, which touches the and the
"configure/*.in" files if it thinks that it is needed. (Causing that autoreconf
is not run because the touched "configure" files is "newer" than the modified
"configure.ac" file.)
* * *
Some older comments - written before comment 1 was available.
libgfortran/acinclude.m4 contains:
if test -f ../libquadmath/libquadmath.la; then
[...];
LIBQUADINCLUDE='- I$(srcdir)/../libquadmath'
else
[...]
LIBQUADINCLUDE=
Thus, the .h file can only be found if ../libquadmath/libquadmath.la is found
or when the .h file is for other reasons in the include path.
There might be also a race condition in building libgfortran and libquadmath;
however, I think (TM) that the following line of Makefile.def should take care
of it:
dependencies = { module=configure-target-libgfortran;
on=all-target-libquadmath; };
Given that many have bootstrapped successfully with and without
--enable-maintainer-mode, I assume either a race condition or that there is
something peculiar on the specific system, which triggers this bug.
