# pull is not a git command - 1.7.6.4 7 messages from 2011-10-25 to 2011-10-25. Participants: Eugene Sajine, Matthieu Moy, Junio C Hamano. Thread: https://gitlist.dev/t/28764 ## Eugene Sajine, 2011-10-25 15:58 Subject: pull is not a git command - 1.7.6.4 Message-ID: URL: https://gitlist.dev/e/CAPZPVFbakHo0hgz3bo%2BSLMuYnQSEA%3Dab%2B4W92%2BLr5Fq4XZy2PA%40mail.gmail.com ``` 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 ``` ## Matthieu Moy, 2011-10-25 16:27 Subject: Re: pull is not a git command - 1.7.6.4 Message-ID: URL: https://gitlist.dev/e/vpqpqhlox45.fsf%40bauges.imag.fr In-Reply-To: ``` Eugene Sajine 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/ ``` ## Junio C Hamano, 2011-10-25 16:45 Subject: Re: pull is not a git command - 1.7.6.4 Message-ID: <7vipnd3trk.fsf@alter.siamese.dyndns.org> URL: https://gitlist.dev/e/7vipnd3trk.fsf%40alter.siamese.dyndns.org In-Reply-To: ``` Eugene Sajine 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 ``` ## Eugene Sajine, 2011-10-25 16:50 Subject: Re: pull is not a git command - 1.7.6.4 Message-ID: URL: https://gitlist.dev/e/CAPZPVFZCQdOsAUMdbcZjmGxVgX5LuKKwcob%3DqBuNmyX7kYwA4A%40mail.gmail.com In-Reply-To: ``` On Tue, Oct 25, 2011 at 12:27 PM, Matthieu Moy wrote: > Eugene Sajine 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 ``` ## Eugene Sajine, 2011-10-25 16:52 Subject: Re: pull is not a git command - 1.7.6.4 Message-ID: URL: https://gitlist.dev/e/CAPZPVFanWTpCDO%2BA0dV4TWUVx-22VjFOdk6f7cmgfU59GqG3sQ%40mail.gmail.com In-Reply-To: <7vipnd3trk.fsf@alter.siamese.dyndns.org> ``` On Tue, Oct 25, 2011 at 12:45 PM, Junio C Hamano wrote: > Eugene Sajine 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 ``` ## Matthieu Moy, 2011-10-25 17:01 Subject: Re: pull is not a git command - 1.7.6.4 Message-ID: URL: https://gitlist.dev/e/vpqr521j98h.fsf%40bauges.imag.fr In-Reply-To: ``` Eugene Sajine writes: > On Tue, Oct 25, 2011 at 12:45 PM, Junio C Hamano 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- 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/ ``` ## Eugene Sajine, 2011-10-25 18:10 Subject: Re: pull is not a git command - 1.7.6.4 Message-ID: URL: https://gitlist.dev/e/CAPZPVFZKNdDcnaVn237gArqdBuc4ek77vxsp8BMaicARBTKqBg%40mail.gmail.com In-Reply-To: ``` On Tue, Oct 25, 2011 at 1:01 PM, Matthieu Moy wrote: > Eugene Sajine writes: > >> On Tue, Oct 25, 2011 at 12:45 PM, Junio C Hamano 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- 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! ```