I'm using snapshot of 2007-11-17 and an already compiled version of autoconf
git from same date (maybe this causes the trouble?).
$ autoconf --version
$ autoconf (GNU Autoconf) 2.61a.299-9066
$ build-aux/git-version-gen . .version; echo
$ UNKNOWN
but when I use my host version:
$ auto
I have an equal problem with autoconf from git. Like Patrick I got autoconf
(GNU Autoconf) UNKNOWN and because of that other software projects won't
compile.
I tried echo 2.61a.2.61a.299-9066 > .version in autoconf dir but autoconf
doesn't seem to use it (maybe I did something wrong).
Best re
Alexander Kahl <[EMAIL PROTECTED]> wrote:
> I have an equal problem with autoconf from git. Like Patrick I got autoconf
> (GNU Autoconf) UNKNOWN and because of that other software projects won't
> compile.
>
> I tried echo 2.61a.2.61a.299-9066 > .version in autoconf dir but autoconf
> doesn't se
Hello Jim,
* Jim Meyering wrote on Sat, Nov 10, 2007 at 10:58:58AM CET:
>
> Hi Patrick,
>
> Maybe you'll see this on the list, or someone will forward a copy to you,
> because you won't get it directly.
I've bounced (remailed in mutt lingo) your messages to Patrick.
Cheers,
Ralf
Patrick Welche <[EMAIL PROTECTED]> wrote:
> There is a potential pitfall when grabbing autoconf via CVS from the
Hi Patrick,
Maybe you'll see this on the list, or someone will forward a copy to you,
because you won't get it directly. Your mail server is rejecting all mail
from the entire class B
Patrick Welche <[EMAIL PROTECTED]> wrote:
> There is a potential pitfall when grabbing autoconf via CVS from the
> git repository which is that VERSION is computed by build-aux/git-version-gen
> which runs git describe. If you checked out via CVS, git rightly complains
> that the checkout isn't a g
