From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk
Subject: Re: Getting an autoconf error with -dev-2
Date: Fri, 09 Dec 2005 17:15:22 +0000 [thread overview]
Message-ID: <EXCHANGE03Ncu9mtisT0000170c@exchange03.csr.com> (raw)
In-Reply-To: <1051209164855.ZM28567@candle.brasslantern.com>
Bart Schaefer wrote:
> cd . && ./.preconfig
> configure.ac:516: error: possibly undefined macro: AC_PROG_EGREP
> ./Util/preconfig: ./.preconfig failed (status 1)
>
> Which version of autoconf are we assuming, now? I have 2.53, which has
> always been sufficient before.
I think 2.59 is fairly common. It seems to have been around a couple of
years.
pws
This message has been scanned for viruses by BlackSpider MailControl - www.blackspider.com
next prev parent reply other threads:[~2005-12-09 17:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-09 16:48 Bart Schaefer
2005-12-09 17:07 ` Clint Adams
2005-12-09 17:15 ` Peter Stephenson [this message]
2005-12-09 17:16 ` Bart Schaefer
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=EXCHANGE03Ncu9mtisT0000170c@exchange03.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).