Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: zsh and autoconf-2.50
- X-seq: zsh-workers 14585
- From: Jos Backus <josb@xxxxxxxxxx>
- To: Clint Adams <clint@xxxxxxx>
- Subject: Re: zsh and autoconf-2.50
- Date: Wed, 30 May 2001 15:44:17 -0700
- Cc: zsh-workers@xxxxxxxxxxxxxx
- In-reply-to: <20010530183400.A3618@xxxxxxxx>; from clint@xxxxxxx on Wed, May 30, 2001 at 06:33:38PM -0400
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <20010530144809.E47866@xxxxxxxxxxxxxxxxxx> <20010530183400.A3618@xxxxxxxx>
- Reply-to: Jos Backus <josb@xxxxxxxxxx>
On Wed, May 30, 2001 at 06:33:38PM -0400, Clint Adams wrote:
> If you just delete the "undefine" lines it complains about, it
> will be happy. However, if you run autoupdate, it will make
> a mess.
Right.
I just installed the previous version of autoconf, 2.13, and lo and behold:
both the m4 undefine and the config.status problem aren't there. So this looks
like some weird interaction between autoconf-2.50 and m4, no?
Off to building zsh with Purify... Has anybody done this before? Is it really
useful? Any tips?
Thanks,
--
Jos Backus _/ _/_/_/ "Modularity is not a hack."
_/ _/ _/ -- D. J. Bernstein
_/ _/_/_/
_/ _/ _/ _/
josb@xxxxxxxxxx _/_/ _/_/_/ use Std::Disclaimer;
Messages sorted by:
Reverse Date,
Date,
Thread,
Author