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

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

[Mun Johl]

Hi,

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?

Thank you,

-- 
Mun

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

[rsbecker]

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.
--Randall

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

[Mun Johl]

Hi Randall,

Thank you for your quick reply.

I'm just wondering... Can I "trick" the compilation process by simply creating a .git directory where I am running 'make'?

Thanks again and best regards,

-- 
Mun

> -----Original Message-----
> From: rsbecker@nexbridge.com <rsbecker@nexbridge.com>
> Sent: Friday, August 11, 2023 1:19 PM
> To: Mun Johl <Mun.Johl@wdc.com>; 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 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.
> --Randall

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

[Mun Johl]

Hi,

Sorry for the additional reply--I should have mentioned that we don't have a git repo yet.  I am just trying to get things setup so that we can create a proper repo and migrate our data.

Best regards,

-- 
Mun

> -----Original Message-----
> From: Mun Johl <Mun.Johl@wdc.com>
> Sent: Friday, August 11, 2023 1:23 PM
> To: rsbecker@nexbridge.com; git@vger.kernel.org
> Subject: RE: "fatal: Not a git repository" issued during 'make' from source code
> 
> Hi Randall,
> 
> Thank you for your quick reply.
> 
> I'm just wondering... Can I "trick" the compilation process by simply creating a .git directory where I am running 'make'?
> 
> Thanks again and best regards,
> 
> --
> Mun
> 
> > -----Original Message-----
> > From: rsbecker@nexbridge.com <rsbecker@nexbridge.com>
> > Sent: Friday, August 11, 2023 1:19 PM
> > To: Mun Johl <Mun.Johl@wdc.com>; 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 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.
> > --Randall

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

[rsbecker]

On Friday, August 11, 2023 4:26 PM, Mon Johl wrote:
>Sorry for the additional reply--I should have mentioned that we don't have
a git repo
>yet.  I am just trying to get things setup so that we can create a proper
repo and
>migrate our data.

Please consult this page:
https://git-scm.com/book/en/v2/Getting-Started-Installing-Git

>> -----Original Message-----
>> From: Mun Johl <Mun.Johl@wdc.com>
>> Sent: Friday, August 11, 2023 1:23 PM
>> To: rsbecker@nexbridge.com; git@vger.kernel.org
>> Subject: RE: "fatal: Not a git repository" issued during 'make' from
>> source code
>>
>> Hi Randall,
>>
>> Thank you for your quick reply.
>>
>> I'm just wondering... Can I "trick" the compilation process by simply
creating a .git
>directory where I am running 'make'?
>>
>> Thanks again and best regards,
>>
>> --
>> Mun
>>
>> > -----Original Message-----
>> > From: rsbecker@nexbridge.com <rsbecker@nexbridge.com>
>> > Sent: Friday, August 11, 2023 1:19 PM
>> > To: Mun Johl <Mun.Johl@wdc.com>; 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 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.
>> > --Randall

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

[Junio C Hamano]

<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?

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

[Junio C Hamano]

Junio C Hamano <gitster@pobox.com> writes:

> <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?

In other words,

    $ mkdir -p /var/tmp/x
    $ cd /var/tmp/x
    $ wget http://www.kernel.org/pub/software/scm/git/testing/git-2.42.0.rc1.tar.xz
    $ tar xf git-2.42.0.rc1.tar.xz
    $ cd git-2.42.0.rc1
    $ make prefix=/var/tmp/local all doc
    $ sudo make prefix=/var/tmp/local install

is what I just did to make sure that a build from our tarball extract
does not require a git repository (it would be a bug to require one,
as it would make it impossible to bootstrap).

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

[rsbecker]

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.

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

[Mun Johl]

Hi Junio and rsbecker,

Please see my comments below.

> 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.

Thank you and regards,

-- 
Mun

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

[rsbecker]

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' ?

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

[Junio C Hamano]

<rsbecker@nexbridge.com> writes:

> Did you run 'make configure' before using 'make prefix=/usr/local all doc' ?

A tarball release ships with configure (built out of configure.in)
included, so that should not be necessary.

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

[rsbecker]

>-----Original Message-----
>From: Junio C Hamano <gitster@pobox.com>
On Friday, August 11, 2023 5:49 PM, Junio C Hamano wrote:
>To: rsbecker@nexbridge.com
>Cc: 'Mun Johl' <Mun.Johl@wdc.com>; git@vger.kernel.org
>Subject: Re: "fatal: Not a git repository" issued during 'make' from source
code
>
><rsbecker@nexbridge.com> writes:
>
>> Did you run 'make configure' before using 'make prefix=/usr/local all
doc' ?
>
>A tarball release ships with configure (built out of configure.in)
included, so that
>should not be necessary.

Thanks. I don't usually build from a tarball. However, the OP did not
indicate that configure was run either.

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

[Mun Johl]

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

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

[rsbecker]

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?
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

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

[Mun Johl]

[-- Attachment #1: Type: text/plain, Size: 4672 bytes --]

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:

$ unxz git-2.41.0.tar.xz
$ tar xvf git-2.41.0.tar
$ cd git-2.41.0
$ make configure

The output of the above command was:

GIT_VERSION = 2.41.0
    GEN configure

$ ./configure --prefix=/usr/local |& tee configure_20230814a_RHEL7.out     // Output is attached as "configure_20230814a_RHEL7.out"
$ make all doc |& tee make_20230814a_RHEL7.out      // Output is attached as "make_20230814a_RHEL7.out"

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


[-- Attachment #2: configure_20230814a_RHEL7.out --]
[-- Type: application/octet-stream, Size: 5344 bytes --]

configure: Setting lib to 'lib' (the default)
configure: Will try -pthread then -lpthread to enable POSIX Threads.
configure: CHECKS for site configuration
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for size_t... yes
checking for working alloca.h... yes
checking for alloca... yes
configure: CHECKS for programs
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking for inline... inline
checking if linker supports -R... no
checking if linker supports -Wl,-rpath,... yes
checking for gar... no
checking for ar... ar
checking for gtar... gtar
checking for gnudiff... no
checking for gdiff... no
checking for diff... diff
checking for asciidoc... no
configure: CHECKS for libraries
checking for SHA1_Init in -lcrypto... yes
checking for curl_global_init in -lcurl... yes
checking for curl-config... curl-config
configure: Setting CURL_LDFLAGS to '-L/usr/local/lib -lcurl'
checking for XML_ParserCreate in -lexpat... yes
checking for iconv in -lc... yes
checking for deflateBound in -lz... yes
checking for socket in -lc... yes
checking for inet_ntop... yes
checking for inet_pton... yes
checking for hstrerror... yes
checking for basename in -lc... yes
checking if libc contains libintl... yes
checking libintl.h usability... yes
checking libintl.h presence... yes
checking for libintl.h... yes
configure: CHECKS for header files
checking sys/select.h usability... yes
checking sys/select.h presence... yes
checking for sys/select.h... yes
checking poll.h usability... yes
checking poll.h presence... yes
checking for poll.h... yes
checking sys/poll.h usability... yes
checking sys/poll.h presence... yes
checking for sys/poll.h... yes
checking for inttypes.h... (cached) yes
checking for old iconv()... no
checking whether iconv omits bom for utf-16 and utf-32... no
configure: CHECKS for typedefs, structures, and compiler characteristics
checking for socklen_t... yes
checking for struct itimerval... yes
checking for struct stat.st_mtimespec.tv_nsec... no
checking for struct stat.st_mtim.tv_nsec... yes
checking for struct dirent.d_type... yes
checking for struct passwd.pw_gecos... yes
checking for struct sockaddr_storage... yes
checking for struct addrinfo... yes
checking for getaddrinfo... yes
checking for library containing getaddrinfo... none required
checking whether the platform regex supports REG_STARTEND... yes
checking whether system succeeds to read fopen'ed directory... yes
checking whether snprintf() and/or vsnprintf() return bogus value... no
checking whether the platform uses typical file type bits... yes
configure: CHECKS for library functions
checking libgen.h usability... yes
checking libgen.h presence... yes
checking for libgen.h... yes
checking paths.h usability... yes
checking paths.h presence... yes
checking for paths.h... yes
checking libcharset.h usability... no
checking libcharset.h presence... no
checking for libcharset.h... no
checking for strings.h... (cached) yes
checking for locale_charset in -liconv... no
checking for locale_charset in -lcharset... no
checking for clock_gettime... yes
checking for library containing clock_gettime... none required
checking for CLOCK_MONOTONIC... yes
checking for sync_file_range... yes
checking for library containing sync_file_range... none required
checking for setitimer... yes
checking for library containing setitimer... none required
checking for strcasestr... yes
checking for library containing strcasestr... none required
checking for memmem... yes
checking for library containing memmem... none required
checking for strlcpy... no
checking for uintmax_t... yes
checking for strtoumax... yes
checking for library containing strtoumax... none required
checking for setenv... yes
checking for library containing setenv... none required
checking for unsetenv... yes
checking for library containing unsetenv... none required
checking for mkdtemp... yes
checking for library containing mkdtemp... none required
checking for initgroups... yes
checking for library containing initgroups... none required
checking for getdelim... yes
checking for library containing getdelim... none required
checking for BSD sysctl... no
checking for POSIX Threads with ''... no
checking for POSIX Threads with '-mt'... no
checking for POSIX Threads with '-pthread'... yes
configure: creating ./config.status
config.status: creating config.mak.autogen
config.status: executing config.mak.autogen commands

[-- Attachment #3: make_20230814a_RHEL7.out --]
[-- Type: application/octet-stream, Size: 24156 bytes --]

    * new build flags
    CC oss-fuzz/fuzz-commit-graph.o
    CC oss-fuzz/fuzz-pack-headers.o
    CC oss-fuzz/fuzz-pack-idx.o
    CC daemon.o
    * new link flags
    CC common-main.o
    CC abspath.o
    CC add-interactive.o
    CC add-patch.o
    CC advice.o
    CC alias.o
    CC alloc.o
    CC apply.o
    CC archive-tar.o
    CC archive-zip.o
    CC archive.o
    * new prefix flags
    CC attr.o
    CC base85.o
    CC bisect.o
    CC blame.o
    CC blob.o
    CC bloom.o
    CC branch.o
    CC bulk-checkin.o
    CC bundle-uri.o
    CC bundle.o
    CC cache-tree.o
    CC cbtree.o
    CC chdir-notify.o
    CC checkout.o
    CC chunk-format.o
    CC color.o
    CC column.o
    CC combine-diff.o
    CC commit-graph.o
    CC commit-reach.o
    CC commit.o
    CC compat/nonblock.o
    CC compat/obstack.o
    CC compat/terminal.o
    CC compat/zlib-uncompress2.o
    CC config.o
    CC connect.o
    CC connected.o
    CC convert.o
    CC copy.o
    CC credential.o
    CC csum-file.o
    CC ctype.o
    CC date.o
    CC decorate.o
    CC delta-islands.o
    CC diagnose.o
    CC diff-delta.o
    CC diff-merges.o
    CC diff-lib.o
    CC diff-no-index.o
    CC diff.o
    CC diffcore-break.o
    CC diffcore-delta.o
    CC diffcore-order.o
    CC diffcore-pickaxe.o
    CC diffcore-rename.o
    CC diffcore-rotate.o
    CC dir-iterator.o
    CC dir.o
    CC editor.o
    CC entry.o
    CC environment.o
    CC ewah/bitmap.o
    CC ewah/ewah_bitmap.o
    CC ewah/ewah_io.o
    CC ewah/ewah_rlw.o
    CC exec-cmd.o
    CC fetch-negotiator.o
    CC fetch-pack.o
    CC fmt-merge-msg.o
    CC fsck.o
    CC fsmonitor.o
    CC fsmonitor-ipc.o
    CC fsmonitor-settings.o
    CC gettext.o
    CC git-zlib.o
    CC gpg-interface.o
    CC graph.o
    CC grep.o
    CC hash-lookup.o
    CC hashmap.o
    GEN command-list.h
    CC help.o
    CC hex.o
    CC hook.o
    CC ident.o
    CC json-writer.o
    CC kwset.o
    CC levenshtein.o
    CC line-log.o
    CC line-range.o
    CC linear-assignment.o
    CC list-objects-filter-options.o
    CC list-objects-filter.o
    CC list-objects.o
    CC ll-merge.o
    CC lockfile.o
    CC log-tree.o
    CC ls-refs.o
    CC mailinfo.o
    CC mailmap.o
    CC match-trees.o
    CC mem-pool.o
    CC merge-blobs.o
    CC merge-ort.o
    CC merge-ort-wrappers.o
    CC merge-recursive.o
    CC merge.o
    CC midx.o
    CC name-hash.o
    CC negotiator/default.o
    CC negotiator/noop.o
    CC negotiator/skipping.o
    CC notes-cache.o
    CC notes-merge.o
    CC notes-utils.o
    CC notes.o
    CC object-file.o
    CC object-name.o
    CC object.o
    CC oid-array.o
    CC oidmap.o
    CC oidset.o
    CC oidtree.o
    CC pack-bitmap-write.o
    CC pack-bitmap.o
    CC pack-check.o
    CC pack-mtimes.o
    CC pack-objects.o
    CC pack-revindex.o
    CC pack-write.o
    CC packfile.o
    CC pager.o
    CC parallel-checkout.o
    CC parse-options-cb.o
    CC parse-options.o
    CC patch-delta.o
    CC patch-ids.o
    CC path.o
    CC pathspec.o
    CC pkt-line.o
    CC preload-index.o
    CC pretty.o
    CC prio-queue.o
    CC progress.o
    CC promisor-remote.o
    CC prompt.o
    CC protocol.o
    CC protocol-caps.o
    CC prune-packed.o
    CC quote.o
    CC range-diff.o
    CC reachable.o
    CC read-cache.o
    CC rebase-interactive.o
    CC rebase.o
    CC ref-filter.o
    CC reflog-walk.o
    CC reflog.o
    CC refs.o
    CC refs/debug.o
    CC refs/files-backend.o
    CC refs/iterator.o
    CC refs/packed-backend.o
    CC refs/ref-cache.o
    CC refspec.o
    CC remote.o
    CC replace-object.o
    CC repo-settings.o
    CC repository.o
    CC rerere.o
    CC reset.o
    CC resolve-undo.o
    CC revision.o
    CC run-command.o
    CC send-pack.o
    CC sequencer.o
    CC serve.o
    CC server-info.o
    CC setup.o
    CC shallow.o
    CC sideband.o
    CC sigchain.o
    CC sparse-index.o
    CC split-index.o
    CC stable-qsort.o
    CC strbuf.o
    CC streaming.o
    CC string-list.o
    CC strmap.o
    CC strvec.o
    CC sub-process.o
    CC submodule-config.o
    CC submodule.o
    CC symlinks.o
    CC tag.o
    CC tempfile.o
    CC thread-utils.o
    CC tmp-objdir.o
    CC trace.o
    CC trace2.o
    CC trace2/tr2_cfg.o
    CC trace2/tr2_cmd_name.o
    CC trace2/tr2_ctr.o
    CC trace2/tr2_dst.o
    CC trace2/tr2_sid.o
    CC trace2/tr2_sysenv.o
    CC trace2/tr2_tbuf.o
    CC trace2/tr2_tgt_event.o
    CC trace2/tr2_tgt_normal.o
    CC trace2/tr2_tgt_perf.o
    CC trace2/tr2_tls.o
    CC trace2/tr2_tmr.o
    CC trailer.o
    CC transport-helper.o
    CC transport.o
    CC tree-diff.o
    CC tree-walk.o
    CC tree.o
    CC unpack-trees.o
    CC upload-pack.o
    CC url.o
    CC urlmatch.o
    CC usage.o
    CC userdiff.o
    CC utf8.o
    CC varint.o
    CC version.o
    CC versioncmp.o
    CC walker.o
    CC wildmatch.o
    CC worktree.o
    CC wrapper.o
    CC write-or-die.o
    CC ws.o
    CC wt-status.o
    CC xdiff-interface.o
    CC unix-socket.o
    CC unix-stream-server.o
    CC compat/simple-ipc/ipc-shared.o
    CC compat/simple-ipc/ipc-unix-socket.o
    CC sha1dc_git.o
    CC sha1dc/sha1.o
    CC sha1dc/ubc_check.o
    CC sha256/block/sha256.o
    CC compat/linux/procinfo.o
    CC compat/fopen.o
    CC compat/strlcpy.o
    CC compat/qsort_s.o
    AR libgit.a
    CC xdiff/xdiffi.o
    CC xdiff/xemit.o
    CC xdiff/xhistogram.o
    CC xdiff/xmerge.o
    CC xdiff/xpatience.o
    CC xdiff/xprepare.o
    CC xdiff/xutils.o
    AR xdiff/lib.a
    CC reftable/basics.o
    CC reftable/error.o
    CC reftable/block.o
    CC reftable/blocksource.o
    CC reftable/iter.o
    CC reftable/publicbasics.o
    CC reftable/merged.o
    CC reftable/pq.o
    CC reftable/reader.o
    CC reftable/record.o
    CC reftable/refname.o
    CC reftable/generic.o
    CC reftable/stack.o
    CC reftable/tree.o
    CC reftable/writer.o
    AR reftable/libreftable.a
    LINK git-daemon
    CC http-backend.o
    LINK git-http-backend
    CC imap-send.o
    CC http.o
    LINK git-imap-send
    CC sh-i18n--envsubst.o
    LINK git-sh-i18n--envsubst
    CC shell.o
    LINK git-shell
    CC http-walker.o
    CC http-fetch.o
    LINK git-http-fetch
    CC http-push.o
    LINK git-http-push
    CC remote-curl.o
    LINK git-remote-http
    LN/CP git-remote-https
    LN/CP git-remote-ftp
    LN/CP git-remote-ftps
    * new script parameters
    GEN git-difftool--helper
    GEN git-filter-branch
    GEN git-merge-octopus
    GEN git-merge-one-file
    GEN git-merge-resolve
    GEN git-mergetool
    GEN git-quiltimport
    GEN git-request-pull
    GEN git-submodule
    GEN git-web--browse
    * new perl-specific parameters
    GEN GIT-PERL-HEADER
    GEN git-archimport
    GEN git-cvsexportcommit
    GEN git-cvsimport
    GEN git-cvsserver
    GEN git-send-email
    GEN git-svn
    * new Python interpreter location
    GEN git-p4
    GEN git-instaweb
    CC git.o
    CC builtin/add.o
    CC builtin/am.o
    CC builtin/annotate.o
    CC builtin/apply.o
    CC builtin/archive.o
    CC builtin/bisect.o
    CC builtin/blame.o
    CC builtin/branch.o
    GEN hook-list.h
    CC builtin/bugreport.o
    CC builtin/bundle.o
    CC builtin/cat-file.o
    CC builtin/check-attr.o
    CC builtin/check-ignore.o
    CC builtin/check-mailmap.o
    CC builtin/check-ref-format.o
    CC builtin/checkout--worker.o
    CC builtin/checkout-index.o
    CC builtin/checkout.o
    CC builtin/clean.o
    CC builtin/clone.o
    CC builtin/column.o
    CC builtin/commit-graph.o
    CC builtin/commit-tree.o
    CC builtin/commit.o
    CC builtin/config.o
    CC builtin/count-objects.o
    CC builtin/credential-cache--daemon.o
    CC builtin/credential-cache.o
    CC builtin/credential-store.o
    CC builtin/credential.o
    CC builtin/describe.o
    CC builtin/diagnose.o
    CC builtin/diff-files.o
    CC builtin/diff-index.o
    CC builtin/diff-tree.o
    CC builtin/diff.o
    CC builtin/difftool.o
    CC builtin/fast-export.o
    CC builtin/fast-import.o
    CC builtin/fetch-pack.o
    CC builtin/fetch.o
    CC builtin/fmt-merge-msg.o
    CC builtin/for-each-ref.o
    CC builtin/for-each-repo.o
    CC builtin/fsck.o
    CC builtin/fsmonitor--daemon.o
    CC builtin/gc.o
    CC builtin/get-tar-commit-id.o
    CC builtin/grep.o
    CC builtin/hash-object.o
    GEN config-list.h
    CC builtin/help.o
    CC builtin/hook.o
    CC builtin/index-pack.o
    CC builtin/init-db.o
    CC builtin/interpret-trailers.o
    CC builtin/log.o
    CC builtin/ls-files.o
    CC builtin/ls-remote.o
    CC builtin/ls-tree.o
    CC builtin/mailinfo.o
    CC builtin/mailsplit.o
    CC builtin/merge-base.o
    CC builtin/merge-file.o
    CC builtin/merge-index.o
    CC builtin/merge-ours.o
    CC builtin/merge-recursive.o
    CC builtin/merge-tree.o
    CC builtin/merge.o
    CC builtin/mktag.o
    CC builtin/mktree.o
    CC builtin/multi-pack-index.o
    CC builtin/mv.o
    CC builtin/name-rev.o
    CC builtin/notes.o
    CC builtin/pack-objects.o
    CC builtin/pack-redundant.o
    CC builtin/pack-refs.o
    CC builtin/patch-id.o
    CC builtin/prune-packed.o
    CC builtin/prune.o
    CC builtin/pull.o
    CC builtin/push.o
    CC builtin/range-diff.o
    CC builtin/read-tree.o
    CC builtin/rebase.o
    CC builtin/receive-pack.o
    CC builtin/reflog.o
    CC builtin/remote-ext.o
    CC builtin/remote-fd.o
    CC builtin/remote.o
    CC builtin/repack.o
    CC builtin/replace.o
    CC builtin/rerere.o
    CC builtin/reset.o
    CC builtin/rev-list.o
    CC builtin/rev-parse.o
    CC builtin/revert.o
    CC builtin/rm.o
    CC builtin/send-pack.o
    CC builtin/shortlog.o
    CC builtin/show-branch.o
    CC builtin/show-index.o
    CC builtin/show-ref.o
    CC builtin/sparse-checkout.o
    CC builtin/stash.o
    CC builtin/stripspace.o
    CC builtin/submodule--helper.o
    CC builtin/symbolic-ref.o
    CC builtin/tag.o
    CC builtin/unpack-file.o
    CC builtin/unpack-objects.o
    CC builtin/update-index.o
    CC builtin/update-ref.o
    CC builtin/update-server-info.o
    CC builtin/upload-archive.o
    CC builtin/upload-pack.o
    CC builtin/var.o
    CC builtin/verify-commit.o
    CC builtin/verify-pack.o
    CC builtin/verify-tag.o
    CC builtin/worktree.o
    CC builtin/write-tree.o
    LINK git
    BUILTIN git-add
    BUILTIN git-am
    BUILTIN git-annotate
    BUILTIN git-apply
    BUILTIN git-archive
    BUILTIN git-bisect
    BUILTIN git-blame
    BUILTIN git-branch
    BUILTIN git-bugreport
    BUILTIN git-bundle
    BUILTIN git-cat-file
    BUILTIN git-check-attr
    BUILTIN git-check-ignore
    BUILTIN git-check-mailmap
    BUILTIN git-check-ref-format
    BUILTIN git-checkout--worker
    BUILTIN git-checkout-index
    BUILTIN git-checkout
    BUILTIN git-clean
    BUILTIN git-clone
    BUILTIN git-column
    BUILTIN git-commit-graph
    BUILTIN git-commit-tree
    BUILTIN git-commit
    BUILTIN git-config
    BUILTIN git-count-objects
    BUILTIN git-credential-cache--daemon
    BUILTIN git-credential-cache
    BUILTIN git-credential-store
    BUILTIN git-credential
    BUILTIN git-describe
    BUILTIN git-diagnose
    BUILTIN git-diff-files
    BUILTIN git-diff-index
    BUILTIN git-diff-tree
    BUILTIN git-diff
    BUILTIN git-difftool
    BUILTIN git-fast-export
    BUILTIN git-fast-import
    BUILTIN git-fetch-pack
    BUILTIN git-fetch
    BUILTIN git-fmt-merge-msg
    BUILTIN git-for-each-ref
    BUILTIN git-for-each-repo
    BUILTIN git-fsck
    BUILTIN git-fsmonitor--daemon
    BUILTIN git-gc
    BUILTIN git-get-tar-commit-id
    BUILTIN git-grep
    BUILTIN git-hash-object
    BUILTIN git-help
    BUILTIN git-hook
    BUILTIN git-index-pack
    BUILTIN git-init-db
    BUILTIN git-interpret-trailers
    BUILTIN git-log
    BUILTIN git-ls-files
    BUILTIN git-ls-remote
    BUILTIN git-ls-tree
    BUILTIN git-mailinfo
    BUILTIN git-mailsplit
    BUILTIN git-merge-base
    BUILTIN git-merge-file
    BUILTIN git-merge-index
    BUILTIN git-merge-ours
    BUILTIN git-merge-recursive
    BUILTIN git-merge-tree
    BUILTIN git-merge
    BUILTIN git-mktag
    BUILTIN git-mktree
    BUILTIN git-multi-pack-index
    BUILTIN git-mv
    BUILTIN git-name-rev
    BUILTIN git-notes
    BUILTIN git-pack-objects
    BUILTIN git-pack-redundant
    BUILTIN git-pack-refs
    BUILTIN git-patch-id
    BUILTIN git-prune-packed
    BUILTIN git-prune
    BUILTIN git-pull
    BUILTIN git-push
    BUILTIN git-range-diff
    BUILTIN git-read-tree
    BUILTIN git-rebase
    BUILTIN git-receive-pack
    BUILTIN git-reflog
    BUILTIN git-remote-ext
    BUILTIN git-remote-fd
    BUILTIN git-remote
    BUILTIN git-repack
    BUILTIN git-replace
    BUILTIN git-rerere
    BUILTIN git-reset
    BUILTIN git-rev-list
    BUILTIN git-rev-parse
    BUILTIN git-revert
    BUILTIN git-rm
    BUILTIN git-send-pack
    BUILTIN git-shortlog
    BUILTIN git-show-branch
    BUILTIN git-show-index
    BUILTIN git-show-ref
    BUILTIN git-sparse-checkout
    BUILTIN git-stash
    BUILTIN git-stripspace
    BUILTIN git-submodule--helper
    BUILTIN git-symbolic-ref
    BUILTIN git-tag
    BUILTIN git-unpack-file
    BUILTIN git-unpack-objects
    BUILTIN git-update-index
    BUILTIN git-update-ref
    BUILTIN git-update-server-info
    BUILTIN git-upload-archive
    BUILTIN git-upload-pack
    BUILTIN git-var
    BUILTIN git-verify-commit
    BUILTIN git-verify-pack
    BUILTIN git-verify-tag
    BUILTIN git-worktree
    BUILTIN git-write-tree
    BUILTIN git-cherry
    BUILTIN git-cherry-pick
    BUILTIN git-format-patch
    BUILTIN git-fsck-objects
    BUILTIN git-init
    BUILTIN git-maintenance
    BUILTIN git-merge-subtree
    BUILTIN git-restore
    BUILTIN git-show
    BUILTIN git-stage
    BUILTIN git-status
    BUILTIN git-switch
    BUILTIN git-version
    BUILTIN git-whatchanged
    GEN git-mergetool--lib
    GEN git-sh-i18n
    GEN git-sh-setup
    CC scalar.o
    LINK scalar
    SUBDIR git-gui
GITGUI_VERSION = 0.21.GITGUI
    * new locations or Tcl/Tk interpreter
    GEN git-gui
    INDEX lib/
    MSGFMT    po/de.msg 579 translated.
    MSGFMT po/pt_pt.msg 550 translated.
    MSGFMT    po/vi.msg 543 translated.
    MSGFMT    po/hu.msg 514 translated.
    MSGFMT    po/nb.msg 474 translated, 39 untranslated.
    MSGFMT    po/sv.msg 547 translated.
    MSGFMT    po/fr.msg 520 translated.
    MSGFMT    po/it.msg 519 translated, 1 untranslated.
    MSGFMT    po/ja.msg 546 translated, 1 untranslated.
    MSGFMT po/pt_br.msg 520 translated.
    MSGFMT    po/bg.msg 565 translated.
    MSGFMT    po/ru.msg 579 translated.
    MSGFMT po/zh_cn.msg 366 translated, 7 fuzzy, 17 untranslated.
    MSGFMT    po/el.msg 381 translated, 4 fuzzy, 6 untranslated.
    SUBDIR gitk-git
    * new Tcl/Tk interpreter location
    GEN gitk-wish
Generating catalog po/de.msg
msgfmt --statistics --tcl po/de.po -l de -d po/
307 translated messages.
Generating catalog po/pt_pt.msg
msgfmt --statistics --tcl po/pt_pt.po -l pt_pt -d po/
311 translated messages.
Generating catalog po/vi.msg
msgfmt --statistics --tcl po/vi.po -l vi -d po/
307 translated messages.
Generating catalog po/ca.msg
msgfmt --statistics --tcl po/ca.po -l ca -d po/
307 translated messages.
Generating catalog po/hu.msg
msgfmt --statistics --tcl po/hu.po -l hu -d po/
277 translated messages, 18 fuzzy translations, 12 untranslated messages.
Generating catalog po/es.msg
msgfmt --statistics --tcl po/es.po -l es -d po/
184 translated messages, 46 fuzzy translations, 77 untranslated messages.
Generating catalog po/sv.msg
msgfmt --statistics --tcl po/sv.po -l sv -d po/
311 translated messages.
Generating catalog po/fr.msg
msgfmt --statistics --tcl po/fr.po -l fr -d po/
311 translated messages.
Generating catalog po/it.msg
msgfmt --statistics --tcl po/it.po -l it -d po/
274 translated messages, 17 fuzzy translations, 16 untranslated messages.
Generating catalog po/ja.msg
msgfmt --statistics --tcl po/ja.po -l ja -d po/
311 translated messages.
Generating catalog po/pt_br.msg
msgfmt --statistics --tcl po/pt_br.po -l pt_br -d po/
279 translated messages, 16 fuzzy translations, 12 untranslated messages.
Generating catalog po/bg.msg
msgfmt --statistics --tcl po/bg.po -l bg -d po/
317 translated messages.
Generating catalog po/ru.msg
msgfmt --statistics --tcl po/ru.po -l ru -d po/
317 translated messages.
Generating catalog po/zh_cn.msg
msgfmt --statistics --tcl po/zh_cn.po -l zh_cn -d po/
317 translated messages.
    SUBDIR templates
    MKDIR -p po/build/locale/pt_PT/LC_MESSAGES
    MSGFMT po/build/locale/pt_PT/LC_MESSAGES/git.mo
    MKDIR -p po/build/locale/de/LC_MESSAGES
    MSGFMT po/build/locale/de/LC_MESSAGES/git.mo
    MKDIR -p po/build/locale/sv/LC_MESSAGES
    MSGFMT po/build/locale/sv/LC_MESSAGES/git.mo
    MKDIR -p po/build/locale/tr/LC_MESSAGES
    MSGFMT po/build/locale/tr/LC_MESSAGES/git.mo
    MKDIR -p po/build/locale/vi/LC_MESSAGES
    MSGFMT po/build/locale/vi/LC_MESSAGES/git.mo
    MKDIR -p po/build/locale/is/LC_MESSAGES
    MSGFMT po/build/locale/is/LC_MESSAGES/git.mo
    MKDIR -p po/build/locale/ca/LC_MESSAGES
    MSGFMT po/build/locale/ca/LC_MESSAGES/git.mo
    MKDIR -p po/build/locale/it/LC_MESSAGES
    MSGFMT po/build/locale/it/LC_MESSAGES/git.mo
    MKDIR -p po/build/locale/ko/LC_MESSAGES
    MSGFMT po/build/locale/ko/LC_MESSAGES/git.mo
    MKDIR -p po/build/locale/es/LC_MESSAGES
    MSGFMT po/build/locale/es/LC_MESSAGES/git.mo
    MKDIR -p po/build/locale/pl/LC_MESSAGES
    MSGFMT po/build/locale/pl/LC_MESSAGES/git.mo
    MKDIR -p po/build/locale/fr/LC_MESSAGES
    MSGFMT po/build/locale/fr/LC_MESSAGES/git.mo
    MKDIR -p po/build/locale/id/LC_MESSAGES
    MSGFMT po/build/locale/id/LC_MESSAGES/git.mo
    MKDIR -p po/build/locale/uk/LC_MESSAGES
    MSGFMT po/build/locale/uk/LC_MESSAGES/git.mo
    MKDIR -p po/build/locale/bg/LC_MESSAGES
    MSGFMT po/build/locale/bg/LC_MESSAGES/git.mo
    MKDIR -p po/build/locale/ru/LC_MESSAGES
    MSGFMT po/build/locale/ru/LC_MESSAGES/git.mo
    MKDIR -p po/build/locale/zh_CN/LC_MESSAGES
    MSGFMT po/build/locale/zh_CN/LC_MESSAGES/git.mo
    MKDIR -p po/build/locale/zh_TW/LC_MESSAGES
    MSGFMT po/build/locale/zh_TW/LC_MESSAGES/git.mo
    MKDIR -p po/build/locale/el/LC_MESSAGES
    MSGFMT po/build/locale/el/LC_MESSAGES/git.mo
    MKDIR -p perl/build/lib
    GEN perl/build/lib/Git.pm
    MKDIR -p perl/build/lib/Git
    GEN perl/build/lib/Git/IndexInfo.pm
    GEN perl/build/lib/Git/Packet.pm
    GEN perl/build/lib/Git/SVN.pm
    GEN perl/build/lib/Git/I18N.pm
    GEN perl/build/lib/Git/LoadCPAN.pm
    MKDIR -p perl/build/lib/Git/LoadCPAN
    GEN perl/build/lib/Git/LoadCPAN/Error.pm
    MKDIR -p perl/build/lib/Git/SVN
    GEN perl/build/lib/Git/SVN/GlobSpec.pm
    GEN perl/build/lib/Git/SVN/Fetcher.pm
    GEN perl/build/lib/Git/SVN/Utils.pm
    GEN perl/build/lib/Git/SVN/Prompt.pm
    GEN perl/build/lib/Git/SVN/Ra.pm
    GEN perl/build/lib/Git/SVN/Editor.pm
    GEN perl/build/lib/Git/SVN/Migration.pm
    GEN perl/build/lib/Git/SVN/Log.pm
    MKDIR -p perl/build/lib/Git/LoadCPAN/Mail
    GEN perl/build/lib/Git/LoadCPAN/Mail/Address.pm
    MKDIR -p perl/build/lib/Git/SVN/Memoize
    GEN perl/build/lib/Git/SVN/Memoize/YAML.pm
    MKDIR -p perl/build/lib/FromCPAN
    GEN perl/build/lib/FromCPAN/Error.pm
    MKDIR -p perl/build/lib/FromCPAN/Mail
    GEN perl/build/lib/FromCPAN/Mail/Address.pm
    CC t/helper/test-fake-ssh.o
    CC reftable/basics_test.o
    CC reftable/block_test.o
    CC reftable/dump.o
    CC reftable/merged_test.o
    CC reftable/pq_test.o
    CC reftable/record_test.o
    CC reftable/readwrite_test.o
    CC reftable/refname_test.o
    CC reftable/stack_test.o
    CC reftable/test_framework.o
    CC reftable/tree_test.o
    AR reftable/libreftable_test.a
    LINK t/helper/test-fake-ssh
    CC t/helper/test-tool.o
    CC t/helper/test-advise.o
    CC t/helper/test-bitmap.o
    CC t/helper/test-bloom.o
    CC t/helper/test-bundle-uri.o
    CC t/helper/test-cache-tree.o
    CC t/helper/test-chmtime.o
    CC t/helper/test-config.o
    CC t/helper/test-crontab.o
    CC t/helper/test-csprng.o
    CC t/helper/test-ctype.o
    CC t/helper/test-date.o
    CC t/helper/test-delta.o
    CC t/helper/test-dir-iterator.o
    CC t/helper/test-drop-caches.o
    CC t/helper/test-dump-cache-tree.o
    CC t/helper/test-dump-fsmonitor.o
    CC t/helper/test-dump-split-index.o
    CC t/helper/test-dump-untracked-cache.o
    CC t/helper/test-env-helper.o
    CC t/helper/test-example-decorate.o
    CC t/helper/test-fast-rebase.o
    CC t/helper/test-fsmonitor-client.o
    CC t/helper/test-genrandom.o
    CC t/helper/test-genzeros.o
    CC t/helper/test-getcwd.o
    CC t/helper/test-hash-speed.o
    CC t/helper/test-hash.o
    CC t/helper/test-hashmap.o
    CC t/helper/test-hexdump.o
    CC t/helper/test-index-version.o
    CC t/helper/test-json-writer.o
    CC t/helper/test-lazy-init-name-hash.o
    CC t/helper/test-match-trees.o
    CC t/helper/test-mergesort.o
    CC t/helper/test-mktemp.o
    CC t/helper/test-oid-array.o
    CC t/helper/test-oidmap.o
    CC t/helper/test-oidtree.o
    CC t/helper/test-online-cpus.o
    CC t/helper/test-pack-mtimes.o
    CC t/helper/test-parse-options.o
    CC t/helper/test-parse-pathspec-file.o
    CC t/helper/test-partial-clone.o
    CC t/helper/test-path-utils.o
    CC t/helper/test-pcre2-config.o
    CC t/helper/test-pkt-line.o
    CC t/helper/test-prio-queue.o
    CC t/helper/test-proc-receive.o
    CC t/helper/test-progress.o
    CC t/helper/test-reach.o
    CC t/helper/test-read-cache.o
    CC t/helper/test-read-graph.o
    CC t/helper/test-read-midx.o
    CC t/helper/test-ref-store.o
    CC t/helper/test-reftable.o
    CC t/helper/test-regex.o
    CC t/helper/test-rot13-filter.o
    CC t/helper/test-repository.o
    CC t/helper/test-revision-walking.o
    CC t/helper/test-run-command.o
    CC t/helper/test-scrap-cache-tree.o
    CC t/helper/test-serve-v2.o
    CC t/helper/test-sha1.o
    CC t/helper/test-sha256.o
    CC t/helper/test-sigchain.o
    CC t/helper/test-simple-ipc.o
    CC t/helper/test-strcmp-offset.o
    CC t/helper/test-string-list.o
    CC t/helper/test-submodule-config.o
    CC t/helper/test-submodule-nested-repo-config.o
    CC t/helper/test-submodule.o
    CC t/helper/test-subprocess.o
    CC t/helper/test-trace2.o
    CC t/helper/test-urlmatch-normalization.o
    CC t/helper/test-userdiff.o
    CC t/helper/test-wildmatch.o
    CC t/helper/test-windows-named-pipe.o
    CC t/helper/test-write-cache.o
    CC t/helper/test-xml-encode.o
    LINK t/helper/test-tool
    MKDIR -p bin-wrappers
    GEN bin-wrappers/git
    GEN bin-wrappers/scalar
    GEN bin-wrappers/git-receive-pack
    GEN bin-wrappers/git-shell
    GEN bin-wrappers/git-upload-archive
    GEN bin-wrappers/git-upload-pack
    GEN bin-wrappers/git-cvsserver
    GEN bin-wrappers/test-fake-ssh
    GEN bin-wrappers/test-tool
    GEN gitweb/gitweb.cgi
    GEN gitweb/static/gitweb.js
    MKDIR -p perl/build/man/man3
    GEN perl/build/man/man3/Git.3pm
make -C Documentation all
fatal: Not a git repository (or any parent up to mount point /tools)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
make[1]: Entering directory `/tools/home/mun/Downloads/GIT/git-2.41.0/Documentation'
    GEN mergetools-list.made
    GEN cmd-list.made
    GEN doc.dep
make[2]: Entering directory `/tools/home/mun/Downloads/GIT/git-2.41.0'
make[2]: `GIT-VERSION-FILE' is up to date.
make[2]: Leaving directory `/tools/home/mun/Downloads/GIT/git-2.41.0'
make[1]: Leaving directory `/tools/home/mun/Downloads/GIT/git-2.41.0/Documentation'
fatal: Not a git repository (or any parent up to mount point /tools)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
make[1]: Entering directory `/tools/home/mun/Downloads/GIT/git-2.41.0/Documentation'
make[2]: Entering directory `/tools/home/mun/Downloads/GIT/git-2.41.0'
make[2]: `GIT-VERSION-FILE' is up to date.
make[2]: Leaving directory `/tools/home/mun/Downloads/GIT/git-2.41.0'
    * new asciidoc flags
    ASCIIDOC git-check-ignore.html
/bin/sh: asciidoc: command not found
make[1]: *** [git-check-ignore.html] Error 127
make[1]: Leaving directory `/tools/home/mun/Downloads/GIT/git-2.41.0/Documentation'
make: *** [doc] Error 2

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

[rsbecker]

On Monday, August 14, 2023 9:15 PM, Mun Johl wrote:
>> 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:
>
>$ unxz git-2.41.0.tar.xz
>$ tar xvf git-2.41.0.tar
>$ cd git-2.41.0
>$ make configure
>
>The output of the above command was:
>
>GIT_VERSION = 2.41.0
>    GEN configure
>
>$ ./configure --prefix=/usr/local |& tee configure_20230814a_RHEL7.out
// Output
>is attached as "configure_20230814a_RHEL7.out"
>$ make all doc |& tee make_20230814a_RHEL7.out      // Output is attached
as
>"make_20230814a_RHEL7.out"
>
>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'.

So this looks just like it is dependencies (like asciidoc), but the
procedure for configuring and running the git make looks correct. Yes?

--Randall

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

[Mun Johl]

Hi all,

... Text Deleted ...

> >> >[Mun] My apologies for not providing that data previously: Yes, I did
> >> >run
> >> 'make
> >> >configure' prior to 'make prefix=/usr/local all doc'.
> 
> So this looks just like it is dependencies (like asciidoc), but the
> procedure for configuring and running the git make looks correct. Yes?

[Mun] Yes.

As it turns out, I was able to get the missing RPMs onto our server.  I reran the build commands and I was able to successfully build 'git' and the documentation.  Oddly, I still got the same "fatal:" messages in the output of 'make'--but apparently the issue was not truly fatal (thankfully).

Now I will move on to migrating our SVN repo to git (but apparently I am missing some Perl modules).

I want to thank all of you for being so helpful!

Best regards,

-- 
Mun


> 
> --Randall

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

[Junio C Hamano]

Mun Johl <Mun.Johl@wdc.com> writes:

> 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.

If building from tarball extract fails with "not a git repository"
there is something very wrong with what you are doing, and we do not
know what it is.

Most likely cause new folks fail to build from the source is lack of
necessary development libraries and packages that need to be
installed in their build environment, but I am reasonably certain
that if a tarball extract build is failing due to their environment,
build in a clone of the source repository would fail for exactly the
same reason.

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

[Mun Johl]

Hi Junio,

> -----Original Message-----
> From: Junio C Hamano <gitster@pobox.com>
> Sent: Friday, August 11, 2023 2:46 PM
> To: Mun Johl <Mun.Johl@wdc.com>
> Cc: rsbecker@nexbridge.com; 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.
> 
> 
> Mun Johl <Mun.Johl@wdc.com> writes:
> 
> > 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.
> 
> If building from tarball extract fails with "not a git repository"
> there is something very wrong with what you are doing, and we do not
> know what it is.
> 
> Most likely cause new folks fail to build from the source is lack of
> necessary development libraries and packages that need to be
> installed in their build environment, but I am reasonably certain
> that if a tarball extract build is failing due to their environment,
> build in a clone of the source repository would fail for exactly the
> same reason.

[Mun] Good point.  I'm certain I don't have all of the requisite packages.  I was expecting to see errors about missing packages, but was thrown off by the fatal error.  I will go back and look closely at the output from 'make' and see if I see any errors prior to the fatal error.

Thank you and regards,

-- 
Mun

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

[Todd Zullinger]

Hi,

Mun Johl wrote:
> I am new to git and am trying to compile git-2.41.0 on RHEL7.

This isn't a direct answer to the question (which Randall
and Junio have covered well), but if you're interested, I
build git-2.41.0 for RHEL/CentOS 7 (as well as newer
RHEL/Rocky/Alma and Fedora release) in the Fedora Copr
("Community projects"):

    https://copr.fedorainfracloud.org/coprs/g/git-maint/git/

I currently maintain the git package in Fedora and try to
ensure it always builds for all supported RHEL releases¹.

For RHEL/CentOS 7, the steps to install would be:

    yum install yum-plugin-copr
    yum copr enable @git-maint/git
    yum install git

The upside is that it's a current git build packaged the
same as the RHEL package.  The downside is that it updates
the RHEL package, which may not be acceptable in your
environment.

It's certainly a big jump from 1.8.3.1 to 2.41.0.  I had
forgotten how ancient the RHEL 7 git package was. :)

Alternately, building a git package for RHEL 7 from the
current Fedora git package is another option, if you'd
rather have an rpm to install on multiple hosts.

¹ I may not continue this due to Red Hat's recent decision
  to restrict access to RHEL source code, unfortunately.

-- 
Todd

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

[Mun Johl]

Hi Todd,

> Hi,
> 
> Mun Johl wrote:
> > I am new to git and am trying to compile git-2.41.0 on RHEL7.
> 
> This isn't a direct answer to the question (which Randall
> and Junio have covered well), but if you're interested, I
> build git-2.41.0 for RHEL/CentOS 7 (as well as newer
> RHEL/Rocky/Alma and Fedora release) in the Fedora Copr
> ("Community projects"):
> 
>     https://copr.fedorainfracloud.org/coprs/g/git-maint/git/
> 
> I currently maintain the git package in Fedora and try to
> ensure it always builds for all supported RHEL releases¹.
> 
> For RHEL/CentOS 7, the steps to install would be:
> 
>     yum install yum-plugin-copr
>     yum copr enable @git-maint/git
>     yum install git
> 
> The upside is that it's a current git build packaged the
> same as the RHEL package.  The downside is that it updates
> the RHEL package, which may not be acceptable in your
> environment.
> 
> It's certainly a big jump from 1.8.3.1 to 2.41.0.  I had
> forgotten how ancient the RHEL 7 git package was. :)
> 
> Alternately, building a git package for RHEL 7 from the
> current Fedora git package is another option, if you'd
> rather have an rpm to install on multiple hosts.
> 
> ¹ I may not continue this due to Red Hat's recent decision
>   to restrict access to RHEL source code, unfortunately.[Mun] 

[Mun] Thank you for the link and the additional information!  I am going to try a little more to see if I can get git compiled from source code; but if I get blocked I may download your build :)  It's nice to have options.

Thank you and best regards,

-- 
Mun