RE: "fatal: Not a git repository" issued during 'make' from source code

From

MJMun Johl <mun.johl@wdc.com>

Date

Aug 15, 2023, 01:14 UTC

Message-ID

<PH0PR04MB8295B799ED69C91BBCCCED3B9C14A@PH0PR04MB8295.namprd04.prod.outlook.com>

In-Reply-To

<045201d9cebf$4f96d260$eec47720$@nexbridge.com>

Hi Randall,

> Rather than asking one line at a time, can you provide the complete log,
> input and output of the attempted operation, including the download and tar?[Mun] 

[Mun] I downloaded "git-2.41.0.tar.xz" from https://mirrors.edge.kernel.org/pub/software/scm/git/ .  Then I ran:

The output of the above command was:

GIT_VERSION = 2.41.0
    GEN configure

I went over the output files but didn't notice anything to cause a fatal error; although, I do have some missing pkgs that I will work on retrieving and installing.  Remember, due to corporate security settings, I cannot simply to a 'yum install' of missing pkgs.

Thank you and regards,

-- 
Mun

> Thanks,
> Randall
> 
> >-----Original Message-----
> >From: Mun Johl <Mun.Johl@wdc.com>
> >Sent: Saturday, August 12, 2023 1:33 AM
> >To: rsbecker@nexbridge.com; 'Junio C Hamano' <gitster@pobox.com>
> >Cc: git@vger.kernel.org
> >Subject: RE: "fatal: Not a git repository" issued during 'make' from source
> code
> >
> >Hi rsbecker,
> >
> >> -----Original Message-----
> >> From: rsbecker@nexbridge.com <rsbecker@nexbridge.com>
> >> Sent: Friday, August 11, 2023 2:46 PM
> >> To: Mun Johl <Mun.Johl@wdc.com>; 'Junio C Hamano' <gitster@pobox.com>
> >> Cc: git@vger.kernel.org
> >> Subject: RE: "fatal: Not a git repository" issued during 'make' from
> >> source code
> >>
> >> CAUTION: This email originated from outside of Western Digital. Do not
> >> click on links or open attachments unless you recognize the sender and
> know that
> >the content is safe.
> >>
> >>
> >> On Friday, August 11, 2023 5:15 PM, Mon Johl wrote:
> >> >> On Friday, August 11, 2023 4:39 PM, Junio C Hamano wrote:
> >> >> >Subject: Re: "fatal: Not a git repository" issued during 'make'
> >> >> >from source
> >> >> code
> >> >> >
> >> >> ><rsbecker@nexbridge.com> writes:
> >> >> >
> >> >> >> On Friday, August 11, 2023 3:57 PM, Mun Johl wrote:
> >> >> >>>I am new to git and am trying to compile git-2.41.0 on RHEL7.
> >> >> >>>When I run
> >> >> >> 'make
> >> >> >>>prefix=/usr/local all doc', I get the following error:
> >> >> >>>
> >> >> >>>fatal: Not a git repository (or any parent up to mount point
> >> >> >>>/tools)
> >> >> >>>
> >> >> >>>Which I infer means that I need to do the build within a git repo.
> >> >> >>>Is
> >> >> that
> >> >> >> correct?  Or
> >> >> >>>have I missed some basic step in the build process?
> >> >> >>
> >> >> >> Yes, you must be in the cloned git repository in order to run
> >> >> >> the
> >> build.
> >> >> >
> >> >> >Shouldn't we be able to build out of a tarball?
> >> >>
> >> >> I don't get the impression he started with a tarball, so
> >> >> subsequently sent the doc ref for that. Using just "make" is not
> >> >> sufficient from a tarball.[Mun]
> >> >
> >> >[Mun] Thank you both for the information you have provided!  It turns
> >> >out I
> >> did in fact
> >> >start from the tar-ball "git-2.41.0.tar.xz" which I downloaded from
> >> >https://mirrors.edge.kernel.org/pub/software/scm/git/ .  And then I
> >> >ran the
> >> 'make'
> >> >command.  The process went something like this (basically identical
> >> >to what
> >> Junio
> >> >documented):
> >> >
> >> >$ tar xf git-2.41.0.tar.xz
> >> >$ cd git-2.41.0
> >> >$ make prefix=/usr/local all doc
> >> >
> >> >And with the above 'make' command I got the fatal error.
> >> >
> >> >I consulted the Getting-Started-Installing-Git web page that rsbecker
> >> referenced, and
> >> >it basically matches the above--except it uses the 'make configure'
> >> process.  So I tried
> >> >that method as well, but when I got to the 'make all doc info' step,
> >> >I
> >> again got the
> >> >same fatal error.
> >> >
> >> >Due to some "security precautions", I am unable to use 'git clone
> >> >https://git.kernel.org/pub/scm/git/git.git' to download the source code.
> >> But I can try
> >> >to figure out a workaround for that if that is my only option at this
> >> >point
> >> to
> >> >successfully compile git.
> >>
> >> Did you run 'make configure' before using 'make prefix=/usr/local all
> doc' ?
> >
> >[Mun] My apologies for not providing that data previously: Yes, I did run
> 'make
> >configure' prior to 'make prefix=/usr/local all doc'.
> >
> >Regards,
> >
> >--
> >Mun