From: Paul Eggert <eggert@cs.ucla.edu>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: Annoyingly cautious make rules
Date: Wed, 30 Nov 2011 14:00:18 -0800 [thread overview]
Message-ID: <4ED6A772.3030101@cs.ucla.edu> (raw)
In-Reply-To: <E1RVs1O-0005dQ-96@fencepost.gnu.org>
On 11/30/11 13:48, Richard Stallman wrote:
> I ran config.status, hoping to avoid the 10 minutes it takes to run
> configure on my machine, since I did that yesterday. But
> config.status ran configure.
That doesn't happen with me (see below).
From the Subject: line, it sounds like you're saying
that a Makefile rule contains a dependency that it shouldn't,
but it's not clear which dependency you're referring to.
Currently we have:
config.status: configure lisp/version.el # This one actually runs 'configure'.
configure: configure.in aclocal.m4
Are any of these dependencies the one that caused your problem?
$ ./config.status
config.status: creating Makefile
config.status: creating lib/Makefile
config.status: creating lib-src/Makefile
config.status: creating oldXMenu/Makefile
config.status: creating doc/emacs/Makefile
config.status: creating doc/misc/Makefile
config.status: creating doc/lispintro/Makefile
config.status: creating doc/lispref/Makefile
config.status: creating src/Makefile
config.status: creating lwlib/Makefile
config.status: creating lisp/Makefile
config.status: creating leim/Makefile
config.status: creating test/automated/Makefile
config.status: creating src/config.h
config.status: src/config.h is unchanged
config.status: executing depfiles commands
config.status: executing mkdirs commands
config.status: executing epaths commands
creating src/epaths.h
[ -r "/home/eggert/src/gnu/emacs/static-checking/src/config.in" ] || ( cd /home/eggert/src/gnu/emacs/static-checking && autoheader )
config.status: executing gdbinit commands
$
next prev parent reply other threads:[~2011-11-30 22:00 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 21:48 Annoyingly cautious make rules Richard Stallman
2011-11-30 22:00 ` Paul Eggert [this message]
2011-12-01 21:54 ` Richard Stallman
2011-12-02 1:35 ` Stefan Monnier
2011-12-02 10:00 ` Paul Eggert
2011-12-01 3:54 ` Eli Zaretskii
2011-12-01 8:50 ` Andreas Schwab
2011-12-02 12:05 ` Richard Stallman
2011-12-02 12:11 ` Andy Wingo
2011-12-02 12:13 ` Andreas Schwab
2011-12-02 14:57 ` Eli Zaretskii
2011-12-02 15:05 ` Andreas Schwab
2011-12-02 15:41 ` Eli Zaretskii
2011-12-03 9:23 ` Richard Stallman
2011-12-02 16:14 ` Stefan Monnier
2011-12-02 16:24 ` Eli Zaretskii
2011-12-02 18:24 ` Paul Eggert
2011-12-02 18:39 ` Glenn Morris
2011-12-02 20:21 ` Paul Eggert
2011-12-02 20:36 ` Stefan Monnier
2011-12-02 21:29 ` Paul Eggert
2011-12-02 23:26 ` Stefan Monnier
2011-12-03 0:34 ` Andreas Schwab
2011-12-03 2:52 ` Paul Eggert
2011-12-03 3:42 ` Stefan Monnier
2011-12-03 3:55 ` Paul Eggert
2011-12-03 5:48 ` Stefan Monnier
2011-12-03 6:35 ` Paul Eggert
2011-12-03 8:49 ` Andreas Schwab
2011-12-03 20:15 ` Paul Eggert
2011-12-03 20:29 ` Andreas Schwab
2011-12-03 20:42 ` Glenn Morris
2011-12-04 15:04 ` Richard Stallman
2011-12-04 16:55 ` Stefan Monnier
2011-12-04 18:57 ` Paul Eggert
2011-12-05 2:53 ` Glenn Morris
2011-12-03 6:45 ` Eli Zaretskii
2011-12-03 20:23 ` Paul Eggert
2011-12-03 4:52 ` Stephen J. Turnbull
2011-12-03 20:34 ` Paul Eggert
2011-12-03 9:23 ` Richard Stallman
2011-12-03 4:26 ` Stephen J. Turnbull
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=4ED6A772.3030101@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=rms@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.