Git development
 help / color / mirror / Atom feed
From: "Björn Steinbrink" <B.Steinbrink@gmx.de>
To: Joi Ellis <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, 6 Feb 2009 06:14:34 +0100	[thread overview]
Message-ID: <20090206051434.GB31491@atjola.homenet> (raw)
In-Reply-To: <Pine.LNX.4.44.0902052238510.4851-100000@localhost.localdomain>

On 2009.02.05 22:45:13 -0600, Joi Ellis wrote:
> On Fri, 6 Feb 2009, Johannes Schindelin wrote:
> 
> > Hi,
> > 
> > On Fri, 6 Feb 2009, Joi Ellis wrote:
> > 
> > > "make all" fails becuase my libaries are old:
> > > 
> > >     LINK git-fast-import
> > > fast-import.o: In function `store_object':
> > > /usr/local/src/git/git/fast-import.c:1086: undefined reference to `deflateBound'
> > > /usr/local/src/git/git/fast-import.c:1109: undefined reference to `deflateBound'
> > 
> > You need to install a newer libz.  (And this is not a chicken & egg 
> > problem.)
> 
> Yes, this *is* a chicken & egg problem.

No, it's not. It would be one if you needed git to update your zlib or
autoconf. But you don't, so you could simply update zlib or autoconf.
There's no circular dependency. You can even just do "make
NO_DEFLATE_BOUND=1" and be done with it...

Björn

  parent reply	other threads:[~2009-02-06  5:16 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
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 [this message]
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=20090206051434.GB31491@atjola.homenet \
    --to=b.steinbrink@gmx.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox