From: <rsbecker@nexbridge.com>
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
Date: Fri, 11 Aug 2023 17:46:28 -0400 [thread overview]
Message-ID: <035b01d9cc9d$4c2168d0$e4643a70$@nexbridge.com> (raw)
In-Reply-To: <SJ0PR04MB82892A7EB350531DBE4701BA9C10A@SJ0PR04MB8289.namprd04.prod.outlook.com>
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' ?
next prev parent reply other threads:[~2023-08-11 21:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 19:57 "fatal: Not a git repository" issued during 'make' from source code Mun Johl
2023-08-11 20:18 ` rsbecker
2023-08-11 20:22 ` Mun Johl
2023-08-11 20:26 ` Mun Johl
2023-08-11 20:41 ` rsbecker
2023-08-11 20:39 ` Junio C Hamano
2023-08-11 20:44 ` Junio C Hamano
2023-08-11 20:46 ` rsbecker
2023-08-11 21:15 ` Mun Johl
2023-08-11 21:46 ` rsbecker [this message]
2023-08-11 21:49 ` Junio C Hamano
2023-08-11 21:51 ` rsbecker
2023-08-12 5:32 ` Mun Johl
2023-08-14 14:54 ` rsbecker
2023-08-15 1:14 ` Mun Johl
2023-08-15 13:51 ` rsbecker
2023-08-16 0:19 ` Mun Johl
2023-08-11 21:46 ` Junio C Hamano
2023-08-12 5:30 ` Mun Johl
2023-08-12 0:54 ` Todd Zullinger
2023-08-12 5:38 ` Mun Johl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='035b01d9cc9d$4c2168d0$e4643a70$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=Mun.Johl@wdc.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.