From: Miles Bader <miles@gnu.org>
To: gyles19@visi.com
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: Chicken/egg problem building from a 'git clone'
Date: Fri, 06 Feb 2009 14:12:03 +0900 [thread overview]
Message-ID: <buobptg6tek.fsf@dhlpc061.dev.necel.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0902052238510.4851-100000@localhost.localdomain> (Joi Ellis's message of "Thu, 5 Feb 2009 22:45:13 -0600 (CST)")
Joi Ellis <gyles19@visi.com> writes:
> Because there is no configure script provided, and because my autoconf
> is considered too old, I simply can't start the build process because
> I can't generate the missing configure script.
Er, why don't you upgrade to a less ancient version of autoconf...?
Autoconf 2.59 (which is what it seems to want) was released like 5 years ago!
-Miles
--
97% of everything is grunge
next prev parent reply other threads:[~2009-02-06 5:14 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 4:09 Chicken/egg problem building from a 'git clone' Joi Ellis
2009-02-06 4:32 ` Johannes Schindelin
2009-02-06 4:45 ` Joi Ellis
2009-02-06 5:12 ` Miles Bader [this message]
2009-02-06 5:36 ` Junio C Hamano
2009-02-06 5:49 ` Miles Bader
2009-02-06 8:12 ` Junio C Hamano
2009-02-06 9:31 ` Miles Bader
2009-02-06 10:28 ` Junio C Hamano
2009-02-06 10:35 ` Miles Bader
2009-02-06 19:25 ` Jeff King
2009-02-06 22:12 ` Junio C Hamano
2009-03-01 15:56 ` Joi Ellis
2009-03-01 16:34 ` Björn Steinbrink
2009-03-05 9:06 ` Andreas Ericsson
2009-03-05 11:37 ` John Tapsell
2009-03-05 12:06 ` Jeff King
2009-03-05 12:38 ` Matthieu Moy
2009-03-05 12:45 ` Jeff King
2009-03-06 10:39 ` Jakub Narebski
2009-03-06 10:51 ` Matthieu Moy
2009-03-06 11:04 ` Johannes Schindelin
2009-03-06 11:27 ` John Tapsell
2009-03-06 12:02 ` asciidoc, was " Johannes Schindelin
2009-03-06 12:28 ` John Tapsell
2009-03-06 13:15 ` Jakub Narebski
2009-03-06 13:39 ` John Tapsell
2009-02-06 5:14 ` Björn Steinbrink
2009-02-06 11:34 ` Johannes Schindelin
2009-02-06 4:44 ` Björn Steinbrink
2009-02-06 19:06 ` Daniel Barkalow
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=buobptg6tek.fsf@dhlpc061.dev.necel.com \
--to=miles@gnu.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gyles19@visi.com \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.