From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: Git help please - checking out old commit doesn't find lib/gnulib.mk.in.
Date: Sun, 12 Nov 2017 20:58:44 -0500 [thread overview]
Message-ID: <jwva7zrrldd.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: 87po8nt5rt.fsf@wanadoo.es
>> Why can Emacs not have a reliable way of cleaning up configuration and
>> build products (and _only_ these) such that a clean build can then be
>> done?
> How the Emacs build system could know the products generated of the
> future? Because this is the problem you faced.
We don't need to solve this impossible problem.
Instead we just need to make a rule in GNUmakefile (which is not
autoconf-generated contrarily to Makefile) to remove all the
auto-generated files of the present.
Stefan
next prev parent reply other threads:[~2017-11-13 1:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-12 18:09 Git help please - checking out old commit doesn't find lib/gnulib.mk.in Alan Mackenzie
2017-11-12 18:22 ` Andreas Schwab
2017-11-12 18:24 ` Óscar Fuentes
2017-11-12 18:25 ` Lele Gaifax
2017-11-12 18:28 ` John Wiegley
2017-11-12 18:29 ` Eli Zaretskii
2017-11-12 20:06 ` Alan Mackenzie
2017-11-12 20:28 ` Eli Zaretskii
2017-11-12 20:40 ` Stefan Monnier
2017-11-12 21:23 ` Paul Eggert
2017-11-12 21:55 ` Alan Mackenzie
2017-11-12 23:51 ` Óscar Fuentes
2017-11-13 1:58 ` Stefan Monnier [this message]
2017-11-13 2:34 ` Óscar Fuentes
2017-11-13 3:17 ` Stefan Monnier
2017-11-13 1:42 ` Yasushi SHOJI
2017-11-13 8:21 ` Andreas Schwab
2017-11-13 3:30 ` Eli Zaretskii
2017-11-13 18:53 ` Alan Mackenzie
2017-11-13 19:13 ` Paul Eggert
2017-11-13 19:31 ` Alan Mackenzie
2017-11-13 19:17 ` Eli Zaretskii
2017-11-13 19:27 ` Alan Mackenzie
2017-11-13 19:35 ` Eli Zaretskii
2017-11-13 20:30 ` Alan Mackenzie
2017-11-13 20:42 ` Eli Zaretskii
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=jwva7zrrldd.fsf-monnier+gmane.emacs.devel@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@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.
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.