From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 37DADC001B0 for ; Tue, 15 Aug 2023 13:52:26 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237339AbjHONvy (ORCPT ); Tue, 15 Aug 2023 09:51:54 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46496 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232075AbjHONvd (ORCPT ); Tue, 15 Aug 2023 09:51:33 -0400 Received: from secure.elehost.com (secure.elehost.com [185.209.179.11]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 62A16110 for ; Tue, 15 Aug 2023 06:51:32 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at secure.elehost.com Received: from Mazikeen (cpebc4dfb928313-cmbc4dfb928310.cpe.net.cable.rogers.com [99.228.251.108] (may be forged)) (authenticated bits=0) by secure.elehost.com (8.15.2/8.15.2/Debian-22ubuntu3) with ESMTPSA id 37FDnC6v1607502 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 15 Aug 2023 13:49:13 GMT Reply-To: From: To: "'Mun Johl'" , "'Junio C Hamano'" Cc: References: <034501d9cc91$069bd360$13d37a20$@nexbridge.com> <034d01d9cc94$df9db0e0$9ed912a0$@nexbridge.com> <035b01d9cc9d$4c2168d0$e4643a70$@nexbridge.com> <045201d9cebf$4f96d260$eec47720$@nexbridge.com> In-Reply-To: Subject: RE: "fatal: Not a git repository" issued during 'make' from source code Date: Tue, 15 Aug 2023 09:51:22 -0400 Organization: Nexbridge Inc. Message-ID: <001001d9cf7f$96a62f50$c3f28df0$@nexbridge.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQGYfaIzxiLvNNliA6NGPhsdV5ubsQMKIH4jAmvty4sCHttM2gLYUX00Ai/ucqYBRNn+cQF3FusEA1pnyOev2GeGEA== Content-Language: en-ca Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org 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 >> >Sent: Saturday, August 12, 2023 1:33 AM >> >To: rsbecker@nexbridge.com; 'Junio C Hamano' >> >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 >> >> Sent: Friday, August 11, 2023 2:46 PM >> >> To: Mun Johl ; 'Junio C Hamano' >> >> >> >> 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 >> >> >> > >> >> >> > 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