unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: eliz@is.elta.co.il, walters@verbum.org, emacs-devel@gnu.org
Subject: Re: config.in
Date: Thu, 18 Apr 2002 12:45:30 -0600 (MDT)	[thread overview]
Message-ID: <200204181845.g3IIjUp00524@aztec.santafe.edu> (raw)
In-Reply-To: <buon0w39loi.fsf@mcspd15.ucom.lsi.nec.co.jp> (message from Miles Bader on 17 Apr 2002 10:08:13 +0900)

    Note that even if these generated files are included, they may _still_
    need the auto* programs, because CVS makes no attempt to preserve
    timestamps, and the Makefile will attempt to regenerate the files
    anyway (though the checked-out contents are actually `up to date').

This does not seem to have been a problem in the past.  For a few
months I did not have the latest Autoconf and could not regenerate
`configure'.  This was not a real problem; I ran ./configure and I
don't think anything tried to run autoconf.

Things may be different now with src/config.in.  There now seems to be
a Make rule to update that file, so it might try to run automatically.
This is no good.

We may need to delete the dependency that would run that Make rule, so
that it only runs on explicit request (or from `dist').  Or install
some sort of touch command instead.

  parent reply	other threads:[~2002-04-18 18:45 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-16 18:24 config.in Eli Zaretskii
2002-04-16 18:45 ` config.in Miles Bader
2002-04-16 19:40   ` config.in Colin Walters
2002-04-16 21:00     ` config.in Eli Zaretskii
2002-04-16 21:21       ` config.in Alfred M. Szmidt
2002-04-17  4:44         ` config.in Eli Zaretskii
2002-04-17  4:59           ` config.in Colin Walters
2002-04-17  5:08           ` config.in Miles Bader
2002-04-17  9:29             ` config.in Andreas Schwab
2002-04-17  0:00       ` config.in Karl Eichwalder
2002-04-17  5:13         ` config.in Eli Zaretskii
2002-04-17  9:24           ` config.in Andreas Schwab
2002-04-17  1:08       ` config.in Miles Bader
2002-04-17  5:33         ` config.in Eli Zaretskii
2002-04-17  5:54           ` config.in Miles Bader
2002-04-17  9:22             ` config.in Eli Zaretskii
2002-04-17  9:28             ` config.in Andreas Schwab
2002-04-17 12:09               ` config.in Miles Bader
2002-04-18 18:45         ` Richard Stallman [this message]
2002-04-19 10:08           ` config.in Andreas Schwab
2002-04-19 12:19             ` config.in Kim F. Storm
2002-04-19 11:42               ` config.in Andreas Schwab
2002-04-19 13:02                 ` config.in Kim F. Storm
2002-04-20 17:26             ` config.in Richard Stallman
2002-04-21 15:58               ` config.in Andreas Schwab
2002-04-22  7:47                 ` config.in Richard Stallman
2002-04-22  9:18                   ` config.in Andreas Schwab
2002-04-23  0:24                     ` config.in Richard Stallman
2002-04-23  9:54                       ` config.in Andreas Schwab
2002-04-24 17:55                         ` config.in Richard Stallman
2002-04-24 18:27                           ` config.in Andreas Schwab
2002-04-26  3:17                             ` config.in Richard Stallman
2002-04-26 14:32                               ` config.in Andreas Schwab
2002-04-26 14:05                             ` config.in Kim F. Storm
2002-04-27 22:41                               ` config.in Richard Stallman
2002-04-17 12:30   ` config.in Pavel Janík
2002-04-17 14:43     ` config.in Eli Zaretskii
2002-04-17 19:34       ` config.in Pavel Janík
2002-04-18 18:45     ` config.in Richard Stallman
2002-04-17 16:05   ` config.in Richard Stallman
2002-04-17 17:13     ` config.in Eli Zaretskii
2002-04-17 17:40       ` config.in Colin Walters
2002-04-17 19:30         ` config.in Pavel Janík

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=200204181845.g3IIjUp00524@aztec.santafe.edu \
    --to=rms@gnu.org \
    --cc=eliz@is.elta.co.il \
    --cc=emacs-devel@gnu.org \
    --cc=walters@verbum.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 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).