unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: make distclean and quail
Date: Mon, 12 Aug 2013 15:01:14 +0300	[thread overview]
Message-ID: <831u5zqfsl.fsf@gnu.org> (raw)
In-Reply-To: <CAAeL0STczH8=0ZeJ3z2ROv39RwWzBo7h_hZA-K17HFe0pGKbtQ@mail.gmail.com>

> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Sun, 11 Aug 2013 23:39:28 +0200
> Cc: Emacs developers <emacs-devel@gnu.org>
> 
> > Perhaps you should always create a log of a build (e.g., with 'tee'),
> > and collect those that fail like this.  Then, when you have a few, we
> > could see what do they have in common.
> 
> I have a log of this one, and the previous (successful) one.  See the
> attached files (the first ~120 lines of the next-to-last boot,
> successful.log, and the last, unsuccesful.log).

So in both cases you typed "make bootstrap", the Makefile's were all
identical, and you still got different results, is that true?  That
would mean you have a Heisenbug of some kind.

There is some difference between the two runs that might give a clue:

  @@ -29,13 +29,22 @@
   make[1]: Leaving directory `/c/Devel/emacs/repo/trunk/lwlib'
   (cd lib;      make  maintainer-clean)
   make[1]: Entering directory `/c/Devel/emacs/repo/trunk/lib'
  +cd .. && make  am--refresh
  +make[2]: Entering directory `/c/Devel/emacs/repo/trunk'
  +[ -r "/c/devel/emacs/repo/trunk/src/config.in" ] || ( cd /c/devel/emacs/repo/trunk && autoheader )
  +make[2]: Nothing to be done for `am--refresh'.
  +make[2]: Leaving directory `/c/Devel/emacs/repo/trunk'
  +make[2]: Entering directory `/c/Devel/emacs/repo/trunk'
  +[ -r "/c/devel/emacs/repo/trunk/src/config.in" ] || ( cd /c/devel/emacs/repo/trunk && autoheader )
  +make[2]: Nothing to be done for `am--refresh'.
  +make[2]: Leaving directory `/c/Devel/emacs/repo/trunk'
   test -z "" || rm -f 
   test -z "libgnu.a " || rm -f libgnu.a 
   rm -f *.o

Any idea why it does "am--refresh" in one case, but not the other?



  reply	other threads:[~2013-08-12 12:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-15 11:41 make distclean and quail Juanma Barranquero
2013-07-15 15:05 ` Paul Eggert
2013-07-15 15:13   ` Juanma Barranquero
2013-07-15 15:42 ` Eli Zaretskii
2013-07-15 15:56   ` Juanma Barranquero
2013-07-15 16:09     ` Eli Zaretskii
2013-07-15 16:18       ` Juanma Barranquero
2013-08-11  2:48       ` Juanma Barranquero
2013-08-11  3:56         ` chad
2013-08-11 17:17         ` Eli Zaretskii
2013-08-11 17:49           ` Juanma Barranquero
2013-08-11 19:25             ` Eli Zaretskii
2013-08-11 21:39               ` Juanma Barranquero
2013-08-12 12:01                 ` Eli Zaretskii [this message]
2013-08-12 15:55                   ` Juanma Barranquero
2013-08-12 16:25                     ` Eli Zaretskii
2013-08-12 16:29                       ` Juanma Barranquero
2013-08-13 18:10                         ` Eli Zaretskii
2013-08-13 22:33                           ` Juanma Barranquero
2013-08-14  2:54                             ` Eli Zaretskii
2013-08-14 15:17                             ` Eli Zaretskii
2013-08-14 16:15                               ` Juanma Barranquero

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=831u5zqfsl.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).