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: Tue, 15 Aug 2023 09:51:22 -0400 [thread overview]
Message-ID: <001001d9cf7f$96a62f50$c3f28df0$@nexbridge.com> (raw)
In-Reply-To: <PH0PR04MB8295B799ED69C91BBCCCED3B9C14A@PH0PR04MB8295.namprd04.prod.outlook.com>
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
next prev parent reply other threads:[~2023-08-15 13:52 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
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 [this message]
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='001001d9cf7f$96a62f50$c3f28df0$@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.