Re: "fatal: index-pack failed" on git-clone
- From
- Fritz Anderson <fritza@uchicago.edu>
- Date
- Jul 8, 2009, 18:22 UTC
- Message-ID
- <4103BA41-39E4-496F-A76F-17D84F30EA21@uchicago.edu>
- In-Reply-To
- <7vskh76pui.fsf@alter.siamese.dyndns.org>
On Jul 8, 2009, at 12:34 PM, Junio C Hamano wrote:
Show 17 quoted lines
> Which makes the initial "sudo git clone..." find git in _your_ path > before > sanitization (and that is why it even starts), but then the path is > nuked > for the git process it launches, and we cannot find git-index-pack > on the > PATH. > > But this should be fine, as git is expected to find git-index-pack > in its > GIT_EXEC_PATH that is compiled in the binary of "git" itself. > > Which makes me suspect that your "git" in /usr/local/bin may be > misconfigured. You might want to check what these tell you. > > $ git --exec-path > $ /usr/local/bin/git --exec-path
Glad to oblige. These are the four possibilities:
$ git --exec-path /usr/local/libexec/git-core $ /usr/local/bin/git --exec-path /usr/local/libexec/git-core $ sudo git --exec-path /usr/local/libexec/git-core $ sudo /usr/local/bin/git --exec-path /usr/local/libexec/git-core $
Same path every time, sudo or not, full path to git or not.
I built git (after installing zlib) simply with "./configure" and "sudo make install".
— F