On Thu, Sep 26, 2002 at 11:03:18AM -0400, Colin Viebrock wrote:
> I'm just wondering if that's a mistake. Does 2.53 contain buggy cache
> code and is downgrading my version of autoconf really the appropriate
> solution? Or was the cache issue solved in a later version, and the
> buildconf messag
On Thu, Sep 26, 2002 at 11:44:37AM -0400, Dan Kalowsky wrote:
> I've been getting this on my OSX machine for awhile. Thats because
> autoconf 2.53 is the default for the dev tools. Seems to be working
> just fine.
>
> Not entirely sure whats "buggy" about it, but I don't keep up on the
> wh
I've been getting this on my OSX machine for awhile. Thats because
autoconf 2.53 is the default for the dev tools. Seems to be working
just fine.
Not entirely sure whats "buggy" about it, but I don't keep up on the
whole autoconf world either.
On Thursday, September 26, 2002, at 11:03 AM, C
On Thu, 26 Sep 2002, Colin Viebrock wrote:
> I run buildconf and get:
>
> ...
> buildconf: autoconf version 2.53 (ok)
> buildconf: Your version of autoconf likely contains buggy cache code.
>Running cvsclean for you.
>To avoid this, install autoconf-2.13 and automake-1.5.
I run buildconf and get:
...
buildconf: autoconf version 2.53 (ok)
buildconf: Your version of autoconf likely contains buggy cache code.
Running cvsclean for you.
To avoid this, install autoconf-2.13 and automake-1.5.
...
I'm just wondering if that's a mistake. Does 2.53 c
