This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/53188] [4.8 Regression] libatomic error: Please use exactly Autoconf 2.64 instead of 2.69
- From: "hp at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 23 May 2012 03:28:08 +0000
- Subject: [Bug bootstrap/53188] [4.8 Regression] libatomic error: Please use exactly Autoconf 2.64 instead of 2.69
- Auto-submitted: auto-generated
- References: <bug-53188-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53188
Hans-Peter Nilsson <hp at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hp at gcc dot gnu.org
--- Comment #5 from Hans-Peter Nilsson <hp at gcc dot gnu.org> 2012-05-23 03:28:08 UTC ---
JFTR.
(In reply to comment #4)
> Something odd's happening, after a git pull and running make in my build dir
Without using "./contrib/gcc_update --touch" this mess up relative file
modification times, causing autotools to run to update e.g. Makefile.in.
> I
> find the source has changed (I didn't do it)
> @@ -48,7 +48,7 @@ DIST_COMMON = $(am__configure_deps) $(srcdir)/../config.guess
> - $(srcdir)/auto-config.h.in $(top_srcdir)/configure
> + $(srcdir)/auto-config.h.in $(top_srcdir)/configure ChangeLog
I recognize that as an autoconf "feature", seen elsewhere.
Maybe just let it have its way?
After all the ChangeLog files are part of a disted tarball.