pull is not a git command - 1.7.6.4

pull is not a git command - 1.7.6.4

[Eugene Sajine]

Hi,


We have built git 1.7.6.4 and we have a following problem with it:

It is localted in a folder /usr/local/git-1.7.6.4/
If the user has both /usr/local/git-1.7.6.4/ and
/usr/local/git-1.7.6.4/bin in $PATH variable then git works fine.
If the user doesn't have the upper level folder in the $PATH then git
cannot execute some commands like "git pull".
It says pull is not a git command. Or git gc complains that repack is
not a git command.

It doesn't seem to be the case with 1.7.4.1

Was there any change between those versions that i missed, or may be
there is some property we have to specify during build?

Thanks,
Eugene

Re: pull is not a git command - 1.7.6.4

[Matthieu Moy]

Eugene Sajine <euguess@gmail.com> writes:

> Hi,
>
>
> We have built git 1.7.6.4 and we have a following problem with it:

Which command did you use to compile it? What does

  git --exec-path

say?

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/

Re: pull is not a git command - 1.7.6.4

[Eugene Sajine]

On Tue, Oct 25, 2011 at 12:27 PM, Matthieu Moy
<Matthieu.Moy@grenoble-inp.fr> wrote:
> Eugene Sajine <euguess@gmail.com> writes:
>
>> Hi,
>>
>>
>> We have built git 1.7.6.4 and we have a following problem with it:
>
> Which command did you use to compile it? What does
>
>  git --exec-path
>
> say?
>
> --
> Matthieu Moy
> http://www-verimag.imag.fr/~moy/
>

I was not building it myself so i cannot say what command exactly was
used, but i will check it.
OTOH git --exec-path shows:
for version 1.7.4.1 that works properly -
/usr/local/git-1.7.4.1/libexec/git-core
For version 1.7.6.4 libexec is located in some other folder...

Let me check what is this all about.

Thanks,
Eugene

Re: pull is not a git command - 1.7.6.4

[Junio C Hamano]

Eugene Sajine <euguess@gmail.com> writes:

> We have built git 1.7.6.4 and we have a following problem with it:
> .,,
> It doesn't seem to be the case with 1.7.4.1
>
> Was there any change between those versions that i missed, or may be
> there is some property we have to specify during build?

Nothing I can think of offhand that you need to specify _differently_
between the build procedures of these two versions.

Just a wild guess. perhaps you specified prefix=/usr/local/git-1.7.4.1/
eons ago when you built and installed 1.7.4.1 like this:

    make prefix=/usr/local/git-1.7.4.1 all install

and then you did it differently when you installed 1.7.6.4, e.g.

    make all
    make prefix=/usr/local/git-1.7.6.4 install

Re: pull is not a git command - 1.7.6.4

[Eugene Sajine]

On Tue, Oct 25, 2011 at 12:45 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Eugene Sajine <euguess@gmail.com> writes:
>
>> We have built git 1.7.6.4 and we have a following problem with it:
>> .,,
>> It doesn't seem to be the case with 1.7.4.1
>>
>> Was there any change between those versions that i missed, or may be
>> there is some property we have to specify during build?
>
> Nothing I can think of offhand that you need to specify _differently_
> between the build procedures of these two versions.
>
> Just a wild guess. perhaps you specified prefix=/usr/local/git-1.7.4.1/
> eons ago when you built and installed 1.7.4.1 like this:
>
>    make prefix=/usr/local/git-1.7.4.1 all install
>
> and then you did it differently when you installed 1.7.6.4, e.g.
>
>    make all
>    make prefix=/usr/local/git-1.7.6.4 install
>
>


Are you saying that the first command is more correct?
I will check it.

Thanks a lot,
Eugene

Re: pull is not a git command - 1.7.6.4

[Matthieu Moy]

Eugene Sajine <euguess@gmail.com> writes:

> On Tue, Oct 25, 2011 at 12:45 PM, Junio C Hamano <gitster@pobox.com> wrote:
>
>> Just a wild guess. perhaps you specified prefix=/usr/local/git-1.7.4.1/
>> eons ago when you built and installed 1.7.4.1 like this:
>>
>>    make prefix=/usr/local/git-1.7.4.1 all install
>>
>> and then you did it differently when you installed 1.7.6.4, e.g.
>>
>>    make all
>>    make prefix=/usr/local/git-1.7.6.4 install
>>
>>
>
>
> Are you saying that the first command is more correct?
> I will check it.

At build time, Git registers the "exec path" (i.e. where to find
git-<command> executables). So, if you run "make all" without specifying
the install path, Git will set an arbitrary exec-path, and the
installation won't work.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/

Re: pull is not a git command - 1.7.6.4

[Eugene Sajine]

On Tue, Oct 25, 2011 at 1:01 PM, Matthieu Moy
<Matthieu.Moy@grenoble-inp.fr> wrote:
> Eugene Sajine <euguess@gmail.com> writes:
>
>> On Tue, Oct 25, 2011 at 12:45 PM, Junio C Hamano <gitster@pobox.com> wrote:
>>
>>> Just a wild guess. perhaps you specified prefix=/usr/local/git-1.7.4.1/
>>> eons ago when you built and installed 1.7.4.1 like this:
>>>
>>>    make prefix=/usr/local/git-1.7.4.1 all install
>>>
>>> and then you did it differently when you installed 1.7.6.4, e.g.
>>>
>>>    make all
>>>    make prefix=/usr/local/git-1.7.6.4 install
>>>
>>>
>>
>>
>> Are you saying that the first command is more correct?
>> I will check it.
>
> At build time, Git registers the "exec path" (i.e. where to find
> git-<command> executables). So, if you run "make all" without specifying
> the install path, Git will set an arbitrary exec-path, and the
> installation won't work.
>
> --
> Matthieu Moy
> http://www-verimag.imag.fr/~moy/
>

Matthieu/Junio,

Thank you very much for your help - there was a mistake made during
the build where the exec path folder was incorrect and unreachable.

Thanks!