From: Andreas Schwab <schwab@suse.de>
Cc: emacs-devel@gnu.org
Subject: Re: config.in
Date: Wed, 24 Apr 2002 20:27:58 +0200 [thread overview]
Message-ID: <je3cxl3qa9.fsf@sykes.suse.de> (raw)
In-Reply-To: <200204241755.g3OHtJx03370@aztec.santafe.edu> (Richard Stallman's message of "Wed, 24 Apr 2002 11:55:19 -0600 (MDT)")
Richard Stallman <rms@gnu.org> writes:
|> I have now replaced the dependency on configure.in by a variable, which
|> can be set to FRC or configure.in to force running autoconf and
|> autoheader.
|>
|> That is a good solution. You can make your .bashrc set the variable,
|> so that configure and config.in will always be updated for you.
This won't work, because make does not override makefile variable from the
environment by default. What people can do, however, is to run `make
MAINT=configure.in' when they modify configure.in to get things rebuilt.
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-24 18:27 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 ` 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 ` Andreas Schwab [this message]
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=je3cxl3qa9.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).