Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Cary Coutant <ccoutant@google.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches <gdb-patches@sourceware.org>,
	Binutils <binutils@sourceware.org>, 	Doug Evans <dje@google.com>
Subject: Re: [PATCH] update automake version to 1.11.6
Date: Mon, 23 Mar 2015 20:21:00 -0000	[thread overview]
Message-ID: <CAHACq4rFJtH_aJgEDzQSSzHhE0nBN+Yktp2MnX7L8yaYMsZpCA@mail.gmail.com> (raw)
In-Reply-To: <20150323124600.GC5438@adacore.com>

> I personally do verify the changes in the configure files,
> for instance, and ask myself whether each hunk I see makes sense
> to me or not. Seeing unrelated changes because others used a different
> version makes that process a little harder (and, most of the time,
> I'll just start over, and push a patch that first regenerates the
> file).

I have two machines, both with automake-1.11.1 configured and built
from the same source, but the two generate ever-so-slightly different
gold/Makefile.in:

--- a/gold/Makefile.in
+++ b/gold/Makefile.in
@@ -70,8 +70,8 @@ subdir = .
 DIST_COMMON = NEWS README ChangeLog $(srcdir)/Makefile.in \
        $(srcdir)/Makefile.am $(top_srcdir)/configure \
        $(am__configure_deps) $(srcdir)/config.in \
-       $(srcdir)/../mkinstalldirs $(top_srcdir)/po/Make-in ffsll.c \
-       ftruncate.c pread.c mremap.c yyscript.h yyscript.c \
+       $(srcdir)/../mkinstalldirs $(top_srcdir)/po/Make-in pread.c \
+       ffsll.c mremap.c ftruncate.c yyscript.h yyscript.c \
        $(srcdir)/../depcomp $(srcdir)/../ylwrap
 ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
 am__aclocal_m4_deps = $(top_srcdir)/../config/depstand.m4 \

I have to filter out this difference every time I run automake at home.

Both generate identical results for gold/testsuite/Makefile.in, though.

Is there a known non-determinism somewhere in automake? Maybe 1.11.6 fixed that.

-cary


  parent reply	other threads:[~2015-03-23 20:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150311094134.GE9455@vapier>
2015-03-14  5:30 ` Mike Frysinger
2015-03-19 12:06   ` Joel Brobecker
2015-03-19 22:59     ` Doug Evans
2015-03-19 23:04       ` Mike Frysinger
2015-03-20 23:58         ` Doug Evans
2015-03-21 19:59           ` Mike Frysinger
2015-03-21 21:29             ` Doug Evans
     [not found]             ` <CAKOQZ8y8aYVM0ncJVfEYBcy1vEUaqLJ+C1un3vC51bpbr=wEfQ@mail.gmail.com>
2015-03-23 12:46               ` Joel Brobecker
2015-03-23 12:57                 ` H.J. Lu
2015-03-23 13:13                   ` Joel Brobecker
2015-03-23 23:46                   ` Alan Modra
2015-03-24  6:16                     ` Mike Frysinger
2015-03-24 17:02                     ` Joseph Myers
2015-03-23 20:21                 ` Cary Coutant [this message]
2015-03-23 20:29                   ` H.J. Lu
2015-03-24  6:15                 ` Mike Frysinger

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=CAHACq4rFJtH_aJgEDzQSSzHhE0nBN+Yktp2MnX7L8yaYMsZpCA@mail.gmail.com \
    --to=ccoutant@google.com \
    --cc=binutils@sourceware.org \
    --cc=brobecker@adacore.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.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