From: Sam Ravnborg <sam@ravnborg.org>
To: git@vger.kernel.org
Subject: Re: git-update-cache:
Date: Wed, 6 Jul 2005 03:11:50 +0200 [thread overview]
Message-ID: <20050706011150.GA9081@mars.ravnborg.org> (raw)
In-Reply-To: <20050705224220.GA22219@mars.ravnborg.org>
On Wed, Jul 06, 2005 at 12:42:20AM +0200, Sam Ravnborg wrote:
> >
> > I receive the following error:
> > git-update-cache: symbol lookup error: git-update-cache: undefined
> > symbol: deflateBound
> >
>
> > open("/usr/lib/libz.so.1", O_RDONLY) = 3
>
> This is the reason.
>
> For a strange reason when git-update-chache was compiled is was linked
> dynamically towards an older libz.so version.
> Latest installed is libz.1.2.2 which includes deflateBound.
> libz.so.1 points at 1.1.4 which does not.
The solution was to let libz.so.1 point to latest libz.so file.
In my gentoo distribution there seems to be inconsistency
if /lib or /usr/lib is used. That was the root cause.
Back to do some useful stuff..
Sam
prev parent reply other threads:[~2005-07-06 6:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-05 21:02 git-update-cache: Sam Ravnborg
2005-07-05 22:42 ` git-update-cache: Sam Ravnborg
2005-07-06 1:11 ` Sam Ravnborg [this message]
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=20050706011150.GA9081@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=git@vger.kernel.org \
/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