From: Andreas Schwab <schwab@suse.de>
Cc: emacs-devel@gnu.org
Subject: Re: config.in
Date: Fri, 19 Apr 2002 13:42:08 +0200 [thread overview]
Message-ID: <jeelhbgbjj.fsf@sykes.suse.de> (raw)
In-Reply-To: <5x1ydbanji.fsf@kfs2.cua.dk> (storm@cua.dk's message of "19 Apr 2002 14:19:29 +0200")
storm@cua.dk (Kim F. Storm) writes:
|> Andreas Schwab <schwab@suse.de> writes:
|>
|> > Richard Stallman <rms@gnu.org> writes:
|> >
|> > |> 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.
|> >
|> > There was always a rule for configure as well, otherwise I wouldn't have
|> > added one for config.in. But the difference with config.in is that it
|> > depends on a third file, src/stamp-h.in, that functions as a timestamp
|> > file, because autoheader does not modify its output if it wouldn't change,
|> > thus to avoid running autoheader again and again the stamp file is needed.
|> > I have already extended make-dist to fix the timestamps for distribution.
|>
|> I think I got lost half way through those changes.... I don't think
|> I'll ever dare adding a new parameter to config.in or configure :-)
You will not ever need to modify config.in any more.
|> May I suggest that you write a short INTRO_CVS file (not to be
|> included in a dist) which explains what tools are needed to
|> reconfigure things (autoconf version etc.), what (config related)
Just use autoconf >= 2.51, as stated in configure.in (AC_PREREQ).
|> files are in CVS, why they are there, and what the dependencies
|> between all those files are.
In addition to autoconf you just need to run autoheader to update
src/config.in. That's all.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE GmbH, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2002-04-19 11:42 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 ` config.in Richard Stallman
2002-04-19 10:08 ` config.in Andreas Schwab
2002-04-19 12:19 ` config.in Kim F. Storm
2002-04-19 11:42 ` Andreas Schwab [this message]
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=jeelhbgbjj.fsf@sykes.suse.de \
--to=schwab@suse.de \
--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 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).