public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/53188] [4.8 Regression] libatomic error: Please use exactly Autoconf 2.64 instead of 2.69
Date: Wed, 02 May 2012 22:14:00 -0000	[thread overview]
Message-ID: <bug-53188-4-VyyjtPyBOO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53188-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53188

--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-05-02 22:13:06 UTC ---
Something odd's happening, after a git pull and running make in my build dir I
find the source has changed (I didn't do it)

diff --git a/libatomic/Makefile.in b/libatomic/Makefile.in
index 470f83b..a016cdf 100644
--- a/libatomic/Makefile.in
+++ b/libatomic/Makefile.in
@@ -48,7 +48,7 @@ DIST_COMMON = $(am__configure_deps) $(srcdir)/../config.guess
\
        $(srcdir)/../install-sh $(srcdir)/../ltmain.sh \
        $(srcdir)/../missing $(srcdir)/../mkinstalldirs \
        $(srcdir)/Makefile.am $(srcdir)/Makefile.in \
-       $(srcdir)/auto-config.h.in $(top_srcdir)/configure
+       $(srcdir)/auto-config.h.in $(top_srcdir)/configure ChangeLog
 ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
 am__aclocal_m4_deps = $(top_srcdir)/../config/acx.m4 \
        $(top_srcdir)/../config/depstand.m4 \


  parent reply	other threads:[~2012-05-02 22:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-02  9:11 [Bug bootstrap/53188] New: " pluto at agmk dot net
2012-05-02 11:27 ` [Bug bootstrap/53188] [4.8 Regression] " rguenth at gcc dot gnu.org
2012-05-02 13:17 ` rth at gcc dot gnu.org
2012-05-02 16:56 ` pinskia at gcc dot gnu.org
2012-05-02 22:14 ` redi at gcc dot gnu.org [this message]
2012-05-23  6:55 ` hp at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-53188-4-VyyjtPyBOO@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).