From: Pete Harlan <pgit@pcharlan.com>
To: horry <qch1695@motorola.com>
Cc: git@vger.kernel.org
Subject: Re: Problems during upgrade git from 1.5.3.2 to latest
Date: Sun, 26 Oct 2008 20:58:32 -0700 [thread overview]
Message-ID: <49053C68.9020901@pcharlan.com> (raw)
In-Reply-To: <20180862.post@talk.nabble.com>
horry wrote:
> Hello ,
> My previous git version is 1.5.3.2 and i perform the suggested commands :
> git clone http://www.kernel.org/pub/scm/git/git.git and it goes well , end
> up with :
>
> ....................................................................
> got d00da833cbeec16da9415e0ac11269594279545a
> Checking 1480 files out...
> 100% (1480/1480) done
>
> Then i perform make in the same directory i performed clone and it shows
> errors .
>
> bfnt47-gx1:/apps/mds_lrt/git/git> make
> GIT_VERSION = 1.6.0.3.517.g759a
> * new build flags or prefix
> CC fast-import.o
> In file included from /usr/include/openssl/ssl.h:179,
> from git-compat-util.h:104,
> from builtin.h:4,
> from fast-import.c:142:
> /usr/include/openssl/kssl.h:72:18: krb5.h: No such file or directory
This is saying that you are missing this header file. On my machine
(Debian Linux "testing") the package that provides that file is libkrb5-dev.
Even if you're not using Debian, or Linux, this page may help you locate
which packages on your system may contain a given missing file:
http://www.debian.org/distrib/packages#search_contents
Entering krb5.h in the "Search the contents of packages" box brings up a
list of packages containing files ending in "krb5.h", one (likely
example of which) is libkrb5-dev.
--Pete
> XXXXXXX:/apps/mds_lrt/git/git> git version
> git version 1.5.3.2
>
> Can someone tell me how to resolve it ?
>
> thanks,
> Horry
prev parent reply other threads:[~2008-10-27 4:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 2:29 Problems during upgrade git from 1.5.3.2 to latest horry
2008-10-27 3:58 ` Pete Harlan [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=49053C68.9020901@pcharlan.com \
--to=pgit@pcharlan.com \
--cc=git@vger.kernel.org \
--cc=qch1695@motorola.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.