From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: PATCH: remove support for autoconf before 2.50
Date: Tue, 06 Jan 2004 12:13:22 +0000 [thread overview]
Message-ID: <25992.1073391202@csr.com> (raw)
Can someone confirm this is a suitable patch for removing support for
old versions of autoconf, together with deleting configure.in which I
will commit at the same time?
Index: zshconfig.ac
===================================================================
RCS file: /cvsroot/zsh/zsh/zshconfig.ac,v
retrieving revision 1.42
diff -u -r1.42 zshconfig.ac
--- zshconfig.ac 13 Nov 2003 14:34:34 -0000 1.42
+++ zshconfig.ac 6 Jan 2004 12:08:52 -0000
@@ -2085,9 +2085,6 @@
done) >${CONFIG_MODULES}
rm -f ${CONFIG_MODULES}.old
EOM
-AC_OUTPUT_COMMANDS(,[if test -z "\$CONFIG_FILES\$CONFIG_HEADERS"; then
-`cat ./${CONFIG_MODULES}.sh && rm -f ./${CONFIG_MODULES}.sh`
-fi])
. ./${CONFIG_MODULES}.sh
CLEAN_MK="${srcdir}/Config/clean.mk"
Index: Etc/zsh-development-guide
===================================================================
RCS file: /cvsroot/zsh/zsh/Etc/zsh-development-guide,v
retrieving revision 1.9
diff -u -r1.9 zsh-development-guide
--- Etc/zsh-development-guide 28 Jun 2001 11:25:41 -0000 1.9
+++ Etc/zsh-development-guide 6 Jan 2004 12:08:52 -0000
@@ -18,10 +18,9 @@
To develop (as opposed to just build) zsh, you'll need a few specialised
tools:
-* GNU autoconf, version 2.12 or later. (Earlier versions mostly work,
- but part of the configuration system now relies on part of the format
- of the config.status files that get generated. See the comments in
- configure.in and at the end of Src/mkmakemod.sh for an explanation.)
+* GNU autoconf, version 2.50 or later. This version contained
+ significant enhancements and arlier versions will no
+ longer work.
* GNU m4. (Required by autoconf.)
--
Peter Stephenson <pws@csr.com> Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK Tel: +44 (0)1223 692070
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.
www.mimesweeper.com
**********************************************************************
next reply other threads:[~2004-01-06 12:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-06 12:13 Peter Stephenson [this message]
2004-01-06 16:11 ` Bart Schaefer
2004-01-06 17:02 ` Peter Stephenson
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=25992.1073391202@csr.com \
--to=pws@csr.com \
--cc=zsh-workers@sunsite.dk \
/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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).