From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: make distclean and quail
Date: Tue, 13 Aug 2013 21:10:14 +0300 [thread overview]
Message-ID: <834natpim1.fsf@gnu.org> (raw)
In-Reply-To: <CAAeL0STTCT5Q1SQtMiwu2_RY=eff+=5PbYjMeDyDeR8Q=pOrQA@mail.gmail.com>
> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Mon, 12 Aug 2013 18:29:13 +0200
> Cc: Emacs developers <emacs-devel@gnu.org>
>
> On Mon, Aug 12, 2013 at 6:25 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>
> > Then I suggest to collect the Makefile's as well, with each log.
>
> Will do.
>
> > The question is: do all of the "bad" builds have this part in them?
>
> Anecdotal evidence* suggests that all bad builds had reconfiguration,
> but not all reconfigurations triggered a bad build.
There's one other player in this drama: config.status. Can you look
inside it and see how it spells srcdir values? Also, please compare
config.status from a good and a bad build.
Are you using MSYS Sed and Gawk? Or is there a chance one or both of
these are MinGW programs?
next prev parent reply other threads:[~2013-08-13 18:10 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=834natpim1.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.