{"thread":{"id":"60106","subject":"\"fatal: Not a git repository\" issued during 'make' from source code","startedAt":"2023-08-11T19:57:28Z","lastAt":"2023-08-16T00:20:01Z","messageCount":21,"participants":["Mun Johl","rsbecker@nexbridge.com","Junio C Hamano","Todd Zullinger"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"480579","messageId":"SJ0PR04MB8289FF1D6BAC59833D922BA89C10A@SJ0PR04MB8289.namprd04.prod.outlook.com","threadId":"60106","inReplyTo":null,"subject":"\"fatal: Not a git repository\" issued during 'make' from source code","fromName":"Mun Johl","fromEmail":"mun.johl@wdc.com","sentAt":"2023-08-11T19:57:23Z","receivedAt":"2023-08-11T19:57:28Z","isPatch":false,"sender":{"key":"mun.johl@wdc.com","avatar":null},"body":"Hi,\n\nI 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:\n\nfatal: Not a git repository (or any parent up to mount point /tools)\n\nWhich 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?\n\nThank you,\n\n-- \nMun\n"},{"id":"480580","messageId":"034501d9cc91$069bd360$13d37a20$@nexbridge.com","threadId":"60106","inReplyTo":"SJ0PR04MB8289FF1D6BAC59833D922BA89C10A@SJ0PR04MB8289.namprd04.prod.outlook.com","subject":"RE: \"fatal: Not a git repository\" issued during 'make' from source code","fromName":"","fromEmail":"rsbecker@nexbridge.com","sentAt":"2023-08-11T20:18:37Z","receivedAt":"2023-08-11T20:18:48Z","isPatch":false,"sender":{"key":"randall.becker@nexbridge.ca","avatar":"https://avatars.githubusercontent.com/u/28956764?v=4"},"body":"On Friday, August 11, 2023 3:57 PM, Mun Johl wrote:\n>I am new to git and am trying to compile git-2.41.0 on RHEL7. When I run\n'make\n>prefix=/usr/local all doc', I get the following error:\n>\n>fatal: Not a git repository (or any parent up to mount point /tools)\n>\n>Which I infer means that I need to do the build within a git repo. Is that\ncorrect? Or\n>have I missed some basic step in the build process?\n\nYes, you must be in the cloned git repository in order to run the build.\n--Randall\n\n"},{"id":"480581","messageId":"SJ0PR04MB8289D45EE7A495B0ED7F69CD9C10A@SJ0PR04MB8289.namprd04.prod.outlook.com","threadId":"60106","inReplyTo":"034501d9cc91$069bd360$13d37a20$@nexbridge.com","subject":"RE: \"fatal: Not a git repository\" issued during 'make' from source code","fromName":"Mun Johl","fromEmail":"mun.johl@wdc.com","sentAt":"2023-08-11T20:22:56Z","receivedAt":"2023-08-11T20:23:04Z","isPatch":false,"sender":{"key":"mun.johl@wdc.com","avatar":null},"body":"Hi Randall,\n\nThank you for your quick reply.\n\nI'm just wondering... Can I \"trick\" the compilation process by simply creating a .git directory where I am running 'make'?\n\nThanks again and best regards,\n\n-- \nMun\n\n> -----Original Message-----\n> From: rsbecker@nexbridge.com \n> Sent: Friday, August 11, 2023 1:19 PM\n> To: Mun Johl ; git@vger.kernel.org\n> Subject: RE: \"fatal: Not a git repository\" issued during 'make' from source code\n> \n> CAUTION: This email originated from outside of Western Digital. Do not click on links or open attachments unless you recognize the\n> sender and know that the content is safe.\n> \n> \n> On Friday, August 11, 2023 3:57 PM, Mun Johl wrote:\n> >I am new to git and am trying to compile git-2.41.0 on RHEL7. When I run\n> 'make\n> >prefix=/usr/local all doc', I get the following error:\n> >\n> >fatal: Not a git repository (or any parent up to mount point /tools)\n> >\n> >Which I infer means that I need to do the build within a git repo. Is that\n> correct? Or\n> >have I missed some basic step in the build process?\n> \n> Yes, you must be in the cloned git repository in order to run the build.\n> --Randall\n\n"},{"id":"480582","messageId":"SJ0PR04MB82893B315F130DCF181D78F49C10A@SJ0PR04MB8289.namprd04.prod.outlook.com","threadId":"60106","inReplyTo":"SJ0PR04MB8289D45EE7A495B0ED7F69CD9C10A@SJ0PR04MB8289.namprd04.prod.outlook.com","subject":"RE: \"fatal: Not a git repository\" issued during 'make' from source code","fromName":"Mun Johl","fromEmail":"mun.johl@wdc.com","sentAt":"2023-08-11T20:26:00Z","receivedAt":"2023-08-11T20:26:05Z","isPatch":false,"sender":{"key":"mun.johl@wdc.com","avatar":null},"body":"Hi,\n\nSorry 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.\n\nBest regards,\n\n-- \nMun\n\n> -----Original Message-----\n> From: Mun Johl \n> Sent: Friday, August 11, 2023 1:23 PM\n> To: rsbecker@nexbridge.com; git@vger.kernel.org\n> Subject: RE: \"fatal: Not a git repository\" issued during 'make' from source code\n> \n> Hi Randall,\n> \n> Thank you for your quick reply.\n> \n> I'm just wondering... Can I \"trick\" the compilation process by simply creating a .git directory where I am running 'make'?\n> \n> Thanks again and best regards,\n> \n> --\n> Mun\n> \n> > -----Original Message-----\n> > From: rsbecker@nexbridge.com \n> > Sent: Friday, August 11, 2023 1:19 PM\n> > To: Mun Johl ; git@vger.kernel.org\n> > Subject: RE: \"fatal: Not a git repository\" issued during 'make' from source code\n> >\n> > CAUTION: This email originated from outside of Western Digital. Do not click on links or open attachments unless you recognize the\n> > sender and know that the content is safe.\n> >\n> >\n> > On Friday, August 11, 2023 3:57 PM, Mun Johl wrote:\n> > >I am new to git and am trying to compile git-2.41.0 on RHEL7. When I run\n> > 'make\n> > >prefix=/usr/local all doc', I get the following error:\n> > >\n> > >fatal: Not a git repository (or any parent up to mount point /tools)\n> > >\n> > >Which I infer means that I need to do the build within a git repo. Is that\n> > correct? Or\n> > >have I missed some basic step in the build process?\n> >\n> > Yes, you must be in the cloned git repository in order to run the build.\n> > --Randall\n\n"},{"id":"480584","messageId":"xmqqr0o9qpon.fsf@gitster.g","threadId":"60106","inReplyTo":"034501d9cc91$069bd360$13d37a20$@nexbridge.com","subject":"Re: \"fatal: Not a git repository\" issued during 'make' from source code","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2023-08-11T20:39:20Z","receivedAt":"2023-08-11T20:39:27Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":" writes:\n\n> On Friday, August 11, 2023 3:57 PM, Mun Johl wrote:\n>>I am new to git and am trying to compile git-2.41.0 on RHEL7. When I run\n> 'make\n>>prefix=/usr/local all doc', I get the following error:\n>>\n>>fatal: Not a git repository (or any parent up to mount point /tools)\n>>\n>>Which I infer means that I need to do the build within a git repo. Is that\n> correct? Or\n>>have I missed some basic step in the build process?\n>\n> Yes, you must be in the cloned git repository in order to run the build.\n\nShouldn't we be able to build out of a tarball?\n"},{"id":"480585","messageId":"034c01d9cc94$30c14960$9243dc20$@nexbridge.com","threadId":"60106","inReplyTo":"SJ0PR04MB82893B315F130DCF181D78F49C10A@SJ0PR04MB8289.namprd04.prod.outlook.com","subject":"RE: \"fatal: Not a git repository\" issued during 'make' from source code","fromName":"","fromEmail":"rsbecker@nexbridge.com","sentAt":"2023-08-11T20:41:17Z","receivedAt":"2023-08-11T20:41:26Z","isPatch":false,"sender":{"key":"randall.becker@nexbridge.ca","avatar":"https://avatars.githubusercontent.com/u/28956764?v=4"},"body":"On Friday, August 11, 2023 4:26 PM, Mon Johl wrote:\n>Sorry for the additional reply--I should have mentioned that we don't have\na git repo\n>yet. I am just trying to get things setup so that we can create a proper\nrepo and\n>migrate our data.\n\nPlease consult this page:\nhttps://git-scm.com/book/en/v2/Getting-Started-Installing-Git\n\n>> -----Original Message-----\n>> From: Mun Johl \n>> Sent: Friday, August 11, 2023 1:23 PM\n>> To: rsbecker@nexbridge.com; git@vger.kernel.org\n>> Subject: RE: \"fatal: Not a git repository\" issued during 'make' from\n>> source code\n>>\n>> Hi Randall,\n>>\n>> Thank you for your quick reply.\n>>\n>> I'm just wondering... Can I \"trick\" the compilation process by simply\ncreating a .git\n>directory where I am running 'make'?\n>>\n>> Thanks again and best regards,\n>>\n>> --\n>> Mun\n>>\n>> > -----Original Message-----\n>> > From: rsbecker@nexbridge.com \n>> > Sent: Friday, August 11, 2023 1:19 PM\n>> > To: Mun Johl ; git@vger.kernel.org\n>> > Subject: RE: \"fatal: Not a git repository\" issued during 'make' from\n>> > source code\n>> >\n>> > CAUTION: This email originated from outside of Western Digital. Do\n>> > not click on links or open attachments unless you recognize the sender\nand know\n>that the content is safe.\n>> >\n>> >\n>> > On Friday, August 11, 2023 3:57 PM, Mun Johl wrote:\n>> > >I am new to git and am trying to compile git-2.41.0 on RHEL7. When\n>> > >I run\n>> > 'make\n>> > >prefix=/usr/local all doc', I get the following error:\n>> > >\n>> > >fatal: Not a git repository (or any parent up to mount point\n>> > >/tools)\n>> > >\n>> > >Which I infer means that I need to do the build within a git repo.\n>> > >Is that\n>> > correct? Or\n>> > >have I missed some basic step in the build process?\n>> >\n>> > Yes, you must be in the cloned git repository in order to run the\nbuild.\n>> > --Randall\n\n"},{"id":"480586","messageId":"xmqqmsyxqpg7.fsf@gitster.g","threadId":"60106","inReplyTo":"xmqqr0o9qpon.fsf@gitster.g","subject":"Re: \"fatal: Not a git repository\" issued during 'make' from source code","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2023-08-11T20:44:24Z","receivedAt":"2023-08-11T20:44:28Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Junio C Hamano writes:\n\n> writes:\n>\n>> On Friday, August 11, 2023 3:57 PM, Mun Johl wrote:\n>>>I am new to git and am trying to compile git-2.41.0 on RHEL7. When I run\n>> 'make\n>>>prefix=/usr/local all doc', I get the following error:\n>>>\n>>>fatal: Not a git repository (or any parent up to mount point /tools)\n>>>\n>>>Which I infer means that I need to do the build within a git repo. Is that\n>> correct? Or\n>>>have I missed some basic step in the build process?\n>>\n>> Yes, you must be in the cloned git repository in order to run the build.\n>\n> Shouldn't we be able to build out of a tarball?\n\nIn other words,\n\n $ mkdir -p /var/tmp/x\n $ cd /var/tmp/x\n $ wget http://www.kernel.org/pub/software/scm/git/testing/git-2.42.0.rc1.tar.xz\n $ tar xf git-2.42.0.rc1.tar.xz\n $ cd git-2.42.0.rc1\n $ make prefix=/var/tmp/local all doc\n $ sudo make prefix=/var/tmp/local install\n\nis what I just did to make sure that a build from our tarball extract\ndoes not require a git repository (it would be a bug to require one,\nas it would make it impossible to bootstrap).\n"},{"id":"480587","messageId":"034d01d9cc94$df9db0e0$9ed912a0$@nexbridge.com","threadId":"60106","inReplyTo":"xmqqr0o9qpon.fsf@gitster.g","subject":"RE: \"fatal: Not a git repository\" issued during 'make' from source code","fromName":"","fromEmail":"rsbecker@nexbridge.com","sentAt":"2023-08-11T20:46:10Z","receivedAt":"2023-08-11T20:46:20Z","isPatch":false,"sender":{"key":"randall.becker@nexbridge.ca","avatar":"https://avatars.githubusercontent.com/u/28956764?v=4"},"body":"On Friday, August 11, 2023 4:39 PM, Junio C Hamano wrote:\n>Subject: Re: \"fatal: Not a git repository\" issued during 'make' from source\ncode\n>\n> writes:\n>\n>> On Friday, August 11, 2023 3:57 PM, Mun Johl wrote:\n>>>I am new to git and am trying to compile git-2.41.0 on RHEL7. When I run\n>> 'make\n>>>prefix=/usr/local all doc', I get the following error:\n>>>\n>>>fatal: Not a git repository (or any parent up to mount point /tools)\n>>>\n>>>Which I infer means that I need to do the build within a git repo. Is\nthat\n>> correct? Or\n>>>have I missed some basic step in the build process?\n>>\n>> Yes, you must be in the cloned git repository in order to run the build.\n>\n>Shouldn't we be able to build out of a tarball?\n\nI don't get the impression he started with a tarball, so subsequently sent\nthe doc ref for that. Using just \"make\" is not sufficient from a tarball.\n\n"},{"id":"480590","messageId":"SJ0PR04MB82892A7EB350531DBE4701BA9C10A@SJ0PR04MB8289.namprd04.prod.outlook.com","threadId":"60106","inReplyTo":"034d01d9cc94$df9db0e0$9ed912a0$@nexbridge.com","subject":"RE: \"fatal: Not a git repository\" issued during 'make' from source code","fromName":"Mun Johl","fromEmail":"mun.johl@wdc.com","sentAt":"2023-08-11T21:15:22Z","receivedAt":"2023-08-11T21:15:30Z","isPatch":false,"sender":{"key":"mun.johl@wdc.com","avatar":null},"body":"Hi Junio and rsbecker,\n\nPlease see my comments below.\n\n> On Friday, August 11, 2023 4:39 PM, Junio C Hamano wrote:\n> >Subject: Re: \"fatal: Not a git repository\" issued during 'make' from source\n> code\n> >\n> > writes:\n> >\n> >> On Friday, August 11, 2023 3:57 PM, Mun Johl wrote:\n> >>>I am new to git and am trying to compile git-2.41.0 on RHEL7. When I run\n> >> 'make\n> >>>prefix=/usr/local all doc', I get the following error:\n> >>>\n> >>>fatal: Not a git repository (or any parent up to mount point /tools)\n> >>>\n> >>>Which I infer means that I need to do the build within a git repo. Is\n> that\n> >> correct? Or\n> >>>have I missed some basic step in the build process?\n> >>\n> >> Yes, you must be in the cloned git repository in order to run the build.\n> >\n> >Shouldn't we be able to build out of a tarball?\n> \n> I don't get the impression he started with a tarball, so subsequently sent\n> the doc ref for that. Using just \"make\" is not sufficient from a tarball.[Mun] \n\n[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):\n\n$ tar xf git-2.41.0.tar.xz\n$ cd git-2.41.0\n$ make prefix=/usr/local all doc\n\nAnd with the above 'make' command I got the fatal error.\n\nI 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.\n\nDue 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.\n\nThank you and regards,\n\n-- \nMun\n\n\n\n"},{"id":"480592","messageId":"xmqqv8dlp80a.fsf@gitster.g","threadId":"60106","inReplyTo":"SJ0PR04MB82892A7EB350531DBE4701BA9C10A@SJ0PR04MB8289.namprd04.prod.outlook.com","subject":"Re: \"fatal: Not a git repository\" issued during 'make' from source code","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2023-08-11T21:46:29Z","receivedAt":"2023-08-11T21:46:35Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Mun Johl writes:\n\n> Due to some \"security precautions\", I am unable to use 'git clone\n> https://git.kernel.org/pub/scm/git/git.git' to download the source\n> code. But I can try to figure out a workaround for that if that\n> is my only option at this point to successfully compile git.\n\nIf building from tarball extract fails with \"not a git repository\"\nthere is something very wrong with what you are doing, and we do not\nknow what it is.\n\nMost likely cause new folks fail to build from the source is lack of\nnecessary development libraries and packages that need to be\ninstalled in their build environment, but I am reasonably certain\nthat if a tarball extract build is failing due to their environment,\nbuild in a clone of the source repository would fail for exactly the\nsame reason.\n"},{"id":"480593","messageId":"035b01d9cc9d$4c2168d0$e4643a70$@nexbridge.com","threadId":"60106","inReplyTo":"SJ0PR04MB82892A7EB350531DBE4701BA9C10A@SJ0PR04MB8289.namprd04.prod.outlook.com","subject":"RE: \"fatal: Not a git repository\" issued during 'make' from source code","fromName":"","fromEmail":"rsbecker@nexbridge.com","sentAt":"2023-08-11T21:46:28Z","receivedAt":"2023-08-11T21:46:40Z","isPatch":false,"sender":{"key":"randall.becker@nexbridge.ca","avatar":"https://avatars.githubusercontent.com/u/28956764?v=4"},"body":"On Friday, August 11, 2023 5:15 PM, Mon Johl wrote:\n>> On Friday, August 11, 2023 4:39 PM, Junio C Hamano wrote:\n>> >Subject: Re: \"fatal: Not a git repository\" issued during 'make' from\n>> >source\n>> code\n>> >\n>> > writes:\n>> >\n>> >> On Friday, August 11, 2023 3:57 PM, Mun Johl wrote:\n>> >>>I am new to git and am trying to compile git-2.41.0 on RHEL7. When\n>> >>>I run\n>> >> 'make\n>> >>>prefix=/usr/local all doc', I get the following error:\n>> >>>\n>> >>>fatal: Not a git repository (or any parent up to mount point\n>> >>>/tools)\n>> >>>\n>> >>>Which I infer means that I need to do the build within a git repo.\n>> >>>Is\n>> that\n>> >> correct? Or\n>> >>>have I missed some basic step in the build process?\n>> >>\n>> >> Yes, you must be in the cloned git repository in order to run the\nbuild.\n>> >\n>> >Shouldn't we be able to build out of a tarball?\n>>\n>> I don't get the impression he started with a tarball, so subsequently\n>> sent the doc ref for that. Using just \"make\" is not sufficient from a\n>> tarball.[Mun]\n>\n>[Mun] Thank you both for the information you have provided! It turns out I\ndid in fact\n>start from the tar-ball \"git-2.41.0.tar.xz\" which I downloaded from\n>https://mirrors.edge.kernel.org/pub/software/scm/git/ . And then I ran the\n'make'\n>command. The process went something like this (basically identical to what\nJunio\n>documented):\n>\n>$ tar xf git-2.41.0.tar.xz\n>$ cd git-2.41.0\n>$ make prefix=/usr/local all doc\n>\n>And with the above 'make' command I got the fatal error.\n>\n>I consulted the Getting-Started-Installing-Git web page that rsbecker\nreferenced, and\n>it basically matches the above--except it uses the 'make configure'\nprocess. So I tried\n>that method as well, but when I got to the 'make all doc info' step, I\nagain got the\n>same fatal error.\n>\n>Due to some \"security precautions\", I am unable to use 'git clone\n>https://git.kernel.org/pub/scm/git/git.git' to download the source code.\nBut I can try\n>to figure out a workaround for that if that is my only option at this point\nto\n>successfully compile git.\n\nDid you run 'make configure' before using 'make prefix=/usr/local all doc' ?\n\n"},{"id":"480596","messageId":"xmqqr0o9p7vj.fsf@gitster.g","threadId":"60106","inReplyTo":"035b01d9cc9d$4c2168d0$e4643a70$@nexbridge.com","subject":"Re: \"fatal: Not a git repository\" issued during 'make' from source code","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2023-08-11T21:49:20Z","receivedAt":"2023-08-11T21:49:25Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":" writes:\n\n> Did you run 'make configure' before using 'make prefix=/usr/local all doc' ?\n\nA tarball release ships with configure (built out of configure.in)\nincluded, so that should not be necessary.\n\n"},{"id":"480597","messageId":"036801d9cc9d$fa5c3920$ef14ab60$@nexbridge.com","threadId":"60106","inReplyTo":"xmqqr0o9p7vj.fsf@gitster.g","subject":"RE: \"fatal: Not a git repository\" issued during 'make' from source code","fromName":"","fromEmail":"rsbecker@nexbridge.com","sentAt":"2023-08-11T21:51:20Z","receivedAt":"2023-08-11T21:51:34Z","isPatch":false,"sender":{"key":"randall.becker@nexbridge.ca","avatar":"https://avatars.githubusercontent.com/u/28956764?v=4"},"body":"\n\n>-----Original Message-----\n>From: Junio C Hamano \nOn Friday, August 11, 2023 5:49 PM, Junio C Hamano wrote:\n>To: rsbecker@nexbridge.com\n>Cc: 'Mun Johl' ; git@vger.kernel.org\n>Subject: Re: \"fatal: Not a git repository\" issued during 'make' from source\ncode\n>\n> writes:\n>\n>> Did you run 'make configure' before using 'make prefix=/usr/local all\ndoc' ?\n>\n>A tarball release ships with configure (built out of configure.in)\nincluded, so that\n>should not be necessary.\n\nThanks. I don't usually build from a tarball. However, the OP did not\nindicate that configure was run either.\n\n"},{"id":"480618","messageId":"ZNbYNxEfPYAB3ILb@pobox.com","threadId":"60106","inReplyTo":"SJ0PR04MB8289FF1D6BAC59833D922BA89C10A@SJ0PR04MB8289.namprd04.prod.outlook.com","subject":"Re: \"fatal: Not a git repository\" issued during 'make' from source code","fromName":"Todd Zullinger","fromEmail":"tmz@pobox.com","sentAt":"2023-08-12T00:54:15Z","receivedAt":"2023-08-12T00:54:26Z","isPatch":false,"sender":{"key":"tmz@pobox.com","avatar":"https://avatars.githubusercontent.com/u/806319?v=4"},"body":"Hi,\n\nMun Johl wrote:\n> I am new to git and am trying to compile git-2.41.0 on RHEL7.\n\nThis isn't a direct answer to the question (which Randall\nand Junio have covered well), but if you're interested, I\nbuild git-2.41.0 for RHEL/CentOS 7 (as well as newer\nRHEL/Rocky/Alma and Fedora release) in the Fedora Copr\n(\"Community projects\"):\n\n https://copr.fedorainfracloud.org/coprs/g/git-maint/git/\n\nI currently maintain the git package in Fedora and try to\nensure it always builds for all supported RHEL releases¹.\n\nFor RHEL/CentOS 7, the steps to install would be:\n\n yum install yum-plugin-copr\n yum copr enable @git-maint/git\n yum install git\n\nThe upside is that it's a current git build packaged the\nsame as the RHEL package. The downside is that it updates\nthe RHEL package, which may not be acceptable in your\nenvironment.\n\nIt's certainly a big jump from 1.8.3.1 to 2.41.0. I had\nforgotten how ancient the RHEL 7 git package was. :)\n\nAlternately, building a git package for RHEL 7 from the\ncurrent Fedora git package is another option, if you'd\nrather have an rpm to install on multiple hosts.\n\n¹ I may not continue this due to Red Hat's recent decision\n to restrict access to RHEL source code, unfortunately.\n\n-- \nTodd\n"},{"id":"480623","messageId":"SJ0PR04MB8289EB7CF0F2EF1803925D929C11A@SJ0PR04MB8289.namprd04.prod.outlook.com","threadId":"60106","inReplyTo":"xmqqv8dlp80a.fsf@gitster.g","subject":"RE: \"fatal: Not a git repository\" issued during 'make' from source code","fromName":"Mun Johl","fromEmail":"mun.johl@wdc.com","sentAt":"2023-08-12T05:30:17Z","receivedAt":"2023-08-12T05:30:24Z","isPatch":false,"sender":{"key":"mun.johl@wdc.com","avatar":null},"body":"Hi Junio,\n\n> -----Original Message-----\n> From: Junio C Hamano \n> Sent: Friday, August 11, 2023 2:46 PM\n> To: Mun Johl \n> Cc: rsbecker@nexbridge.com; git@vger.kernel.org\n> Subject: Re: \"fatal: Not a git repository\" issued during 'make' from source code\n> \n> CAUTION: This email originated from outside of Western Digital. Do not click on links or open attachments unless you recognize the\n> sender and know that the content is safe.\n> \n> \n> Mun Johl writes:\n> \n> > Due to some \"security precautions\", I am unable to use 'git clone\n> > https://git.kernel.org/pub/scm/git/git.git' to download the source\n> > code. But I can try to figure out a workaround for that if that\n> > is my only option at this point to successfully compile git.\n> \n> If building from tarball extract fails with \"not a git repository\"\n> there is something very wrong with what you are doing, and we do not\n> know what it is.\n> \n> Most likely cause new folks fail to build from the source is lack of\n> necessary development libraries and packages that need to be\n> installed in their build environment, but I am reasonably certain\n> that if a tarball extract build is failing due to their environment,\n> build in a clone of the source repository would fail for exactly the\n> same reason.\n\n[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.\n\nThank you and regards,\n\n-- \nMun\n"},{"id":"480624","messageId":"SJ0PR04MB82897032646F100BCC9001669C11A@SJ0PR04MB8289.namprd04.prod.outlook.com","threadId":"60106","inReplyTo":"035b01d9cc9d$4c2168d0$e4643a70$@nexbridge.com","subject":"RE: \"fatal: Not a git repository\" issued during 'make' from source code","fromName":"Mun Johl","fromEmail":"mun.johl@wdc.com","sentAt":"2023-08-12T05:32:53Z","receivedAt":"2023-08-12T05:32:58Z","isPatch":false,"sender":{"key":"mun.johl@wdc.com","avatar":null},"body":"Hi rsbecker,\n\n> -----Original Message-----\n> From: rsbecker@nexbridge.com \n> Sent: Friday, August 11, 2023 2:46 PM\n> To: Mun Johl ; 'Junio C Hamano' \n> Cc: git@vger.kernel.org\n> Subject: RE: \"fatal: Not a git repository\" issued during 'make' from source code\n> \n> CAUTION: This email originated from outside of Western Digital. Do not click on links or open attachments unless you recognize the\n> sender and know that the content is safe.\n> \n> \n> On Friday, August 11, 2023 5:15 PM, Mon Johl wrote:\n> >> On Friday, August 11, 2023 4:39 PM, Junio C Hamano wrote:\n> >> >Subject: Re: \"fatal: Not a git repository\" issued during 'make' from\n> >> >source\n> >> code\n> >> >\n> >> > writes:\n> >> >\n> >> >> On Friday, August 11, 2023 3:57 PM, Mun Johl wrote:\n> >> >>>I am new to git and am trying to compile git-2.41.0 on RHEL7. When\n> >> >>>I run\n> >> >> 'make\n> >> >>>prefix=/usr/local all doc', I get the following error:\n> >> >>>\n> >> >>>fatal: Not a git repository (or any parent up to mount point\n> >> >>>/tools)\n> >> >>>\n> >> >>>Which I infer means that I need to do the build within a git repo.\n> >> >>>Is\n> >> that\n> >> >> correct? Or\n> >> >>>have I missed some basic step in the build process?\n> >> >>\n> >> >> Yes, you must be in the cloned git repository in order to run the\n> build.\n> >> >\n> >> >Shouldn't we be able to build out of a tarball?\n> >>\n> >> I don't get the impression he started with a tarball, so subsequently\n> >> sent the doc ref for that. Using just \"make\" is not sufficient from a\n> >> tarball.[Mun]\n> >\n> >[Mun] Thank you both for the information you have provided! It turns out I\n> did in fact\n> >start from the tar-ball \"git-2.41.0.tar.xz\" which I downloaded from\n> >https://mirrors.edge.kernel.org/pub/software/scm/git/ . And then I ran the\n> 'make'\n> >command. The process went something like this (basically identical to what\n> Junio\n> >documented):\n> >\n> >$ tar xf git-2.41.0.tar.xz\n> >$ cd git-2.41.0\n> >$ make prefix=/usr/local all doc\n> >\n> >And with the above 'make' command I got the fatal error.\n> >\n> >I consulted the Getting-Started-Installing-Git web page that rsbecker\n> referenced, and\n> >it basically matches the above--except it uses the 'make configure'\n> process. So I tried\n> >that method as well, but when I got to the 'make all doc info' step, I\n> again got the\n> >same fatal error.\n> >\n> >Due to some \"security precautions\", I am unable to use 'git clone\n> >https://git.kernel.org/pub/scm/git/git.git' to download the source code.\n> But I can try\n> >to figure out a workaround for that if that is my only option at this point\n> to\n> >successfully compile git.\n> \n> Did you run 'make configure' before using 'make prefix=/usr/local all doc' ?\n\n[Mun] My apologies for not providing that data previously: Yes, I did run 'make configure' prior to 'make prefix=/usr/local all doc'.\n\nRegards,\n\n-- \nMun\n\n"},{"id":"480626","messageId":"SJ0PR04MB8289E60CA76DF65C17A79DF49C11A@SJ0PR04MB8289.namprd04.prod.outlook.com","threadId":"60106","inReplyTo":"ZNbYNxEfPYAB3ILb@pobox.com","subject":"RE: \"fatal: Not a git repository\" issued during 'make' from source code","fromName":"Mun Johl","fromEmail":"mun.johl@wdc.com","sentAt":"2023-08-12T05:38:39Z","receivedAt":"2023-08-12T05:39:05Z","isPatch":false,"sender":{"key":"mun.johl@wdc.com","avatar":null},"body":"Hi Todd,\n\n> Hi,\n> \n> Mun Johl wrote:\n> > I am new to git and am trying to compile git-2.41.0 on RHEL7.\n> \n> This isn't a direct answer to the question (which Randall\n> and Junio have covered well), but if you're interested, I\n> build git-2.41.0 for RHEL/CentOS 7 (as well as newer\n> RHEL/Rocky/Alma and Fedora release) in the Fedora Copr\n> (\"Community projects\"):\n> \n> https://copr.fedorainfracloud.org/coprs/g/git-maint/git/\n> \n> I currently maintain the git package in Fedora and try to\n> ensure it always builds for all supported RHEL releases¹.\n> \n> For RHEL/CentOS 7, the steps to install would be:\n> \n> yum install yum-plugin-copr\n> yum copr enable @git-maint/git\n> yum install git\n> \n> The upside is that it's a current git build packaged the\n> same as the RHEL package. The downside is that it updates\n> the RHEL package, which may not be acceptable in your\n> environment.\n> \n> It's certainly a big jump from 1.8.3.1 to 2.41.0. I had\n> forgotten how ancient the RHEL 7 git package was. :)\n> \n> Alternately, building a git package for RHEL 7 from the\n> current Fedora git package is another option, if you'd\n> rather have an rpm to install on multiple hosts.\n> \n> ¹ I may not continue this due to Red Hat's recent decision\n> to restrict access to RHEL source code, unfortunately.[Mun] \n\n[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.\n\nThank you and best regards,\n\n-- \nMun\n\n"},{"id":"480647","messageId":"045201d9cebf$4f96d260$eec47720$@nexbridge.com","threadId":"60106","inReplyTo":"SJ0PR04MB82897032646F100BCC9001669C11A@SJ0PR04MB8289.namprd04.prod.outlook.com","subject":"RE: \"fatal: Not a git repository\" issued during 'make' from source code","fromName":"","fromEmail":"rsbecker@nexbridge.com","sentAt":"2023-08-14T14:54:59Z","receivedAt":"2023-08-14T14:56:00Z","isPatch":false,"sender":{"key":"randall.becker@nexbridge.ca","avatar":"https://avatars.githubusercontent.com/u/28956764?v=4"},"body":"Rather than asking one line at a time, can you provide the complete log,\ninput and output of the attempted operation, including the download and tar?\nThanks,\nRandall\n\n>-----Original Message-----\n>From: Mun Johl \n>Sent: Saturday, August 12, 2023 1:33 AM\n>To: rsbecker@nexbridge.com; 'Junio C Hamano' \n>Cc: git@vger.kernel.org\n>Subject: RE: \"fatal: Not a git repository\" issued during 'make' from source\ncode\n>\n>Hi rsbecker,\n>\n>> -----Original Message-----\n>> From: rsbecker@nexbridge.com \n>> Sent: Friday, August 11, 2023 2:46 PM\n>> To: Mun Johl ; 'Junio C Hamano' \n>> Cc: git@vger.kernel.org\n>> Subject: RE: \"fatal: Not a git repository\" issued during 'make' from\n>> source code\n>>\n>> CAUTION: This email originated from outside of Western Digital. Do not\n>> click on links or open attachments unless you recognize the sender and\nknow that\n>the content is safe.\n>>\n>>\n>> On Friday, August 11, 2023 5:15 PM, Mon Johl wrote:\n>> >> On Friday, August 11, 2023 4:39 PM, Junio C Hamano wrote:\n>> >> >Subject: Re: \"fatal: Not a git repository\" issued during 'make'\n>> >> >from source\n>> >> code\n>> >> >\n>> >> > writes:\n>> >> >\n>> >> >> On Friday, August 11, 2023 3:57 PM, Mun Johl wrote:\n>> >> >>>I am new to git and am trying to compile git-2.41.0 on RHEL7.\n>> >> >>>When I run\n>> >> >> 'make\n>> >> >>>prefix=/usr/local all doc', I get the following error:\n>> >> >>>\n>> >> >>>fatal: Not a git repository (or any parent up to mount point\n>> >> >>>/tools)\n>> >> >>>\n>> >> >>>Which I infer means that I need to do the build within a git repo.\n>> >> >>>Is\n>> >> that\n>> >> >> correct? Or\n>> >> >>>have I missed some basic step in the build process?\n>> >> >>\n>> >> >> Yes, you must be in the cloned git repository in order to run\n>> >> >> the\n>> build.\n>> >> >\n>> >> >Shouldn't we be able to build out of a tarball?\n>> >>\n>> >> I don't get the impression he started with a tarball, so\n>> >> subsequently sent the doc ref for that. Using just \"make\" is not\n>> >> sufficient from a tarball.[Mun]\n>> >\n>> >[Mun] Thank you both for the information you have provided! It turns\n>> >out I\n>> did in fact\n>> >start from the tar-ball \"git-2.41.0.tar.xz\" which I downloaded from\n>> >https://mirrors.edge.kernel.org/pub/software/scm/git/ . And then I\n>> >ran the\n>> 'make'\n>> >command. The process went something like this (basically identical\n>> >to what\n>> Junio\n>> >documented):\n>> >\n>> >$ tar xf git-2.41.0.tar.xz\n>> >$ cd git-2.41.0\n>> >$ make prefix=/usr/local all doc\n>> >\n>> >And with the above 'make' command I got the fatal error.\n>> >\n>> >I consulted the Getting-Started-Installing-Git web page that rsbecker\n>> referenced, and\n>> >it basically matches the above--except it uses the 'make configure'\n>> process. So I tried\n>> >that method as well, but when I got to the 'make all doc info' step,\n>> >I\n>> again got the\n>> >same fatal error.\n>> >\n>> >Due to some \"security precautions\", I am unable to use 'git clone\n>> >https://git.kernel.org/pub/scm/git/git.git' to download the source code.\n>> But I can try\n>> >to figure out a workaround for that if that is my only option at this\n>> >point\n>> to\n>> >successfully compile git.\n>>\n>> Did you run 'make configure' before using 'make prefix=/usr/local all\ndoc' ?\n>\n>[Mun] My apologies for not providing that data previously: Yes, I did run\n'make\n>configure' prior to 'make prefix=/usr/local all doc'.\n>\n>Regards,\n>\n>--\n>Mun\n\n"},{"id":"480667","messageId":"PH0PR04MB8295B799ED69C91BBCCCED3B9C14A@PH0PR04MB8295.namprd04.prod.outlook.com","threadId":"60106","inReplyTo":"045201d9cebf$4f96d260$eec47720$@nexbridge.com","subject":"RE: \"fatal: Not a git repository\" issued during 'make' from source code","fromName":"Mun Johl","fromEmail":"mun.johl@wdc.com","sentAt":"2023-08-15T01:14:52Z","receivedAt":"2023-08-15T01:15:31Z","isPatch":false,"sender":{"key":"mun.johl@wdc.com","avatar":null},"body":"Hi Randall,\n\n> Rather than asking one line at a time, can you provide the complete log,\n> input and output of the attempted operation, including the download and tar?[Mun] \n\n[Mun] I downloaded \"git-2.41.0.tar.xz\" from https://mirrors.edge.kernel.org/pub/software/scm/git/ . Then I ran:\n\n$ unxz git-2.41.0.tar.xz\n$ tar xvf git-2.41.0.tar\n$ cd git-2.41.0\n$ make configure\n\nThe output of the above command was:\n\nGIT_VERSION = 2.41.0\n GEN configure\n\n$ ./configure --prefix=/usr/local |& tee configure_20230814a_RHEL7.out // Output is attached as \"configure_20230814a_RHEL7.out\"\n$ make all doc |& tee make_20230814a_RHEL7.out // Output is attached as \"make_20230814a_RHEL7.out\"\n\nI 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.\n\nThank you and regards,\n\n-- \nMun\n\n> Thanks,\n> Randall\n> \n> >-----Original Message-----\n> >From: Mun Johl \n> >Sent: Saturday, August 12, 2023 1:33 AM\n> >To: rsbecker@nexbridge.com; 'Junio C Hamano' \n> >Cc: git@vger.kernel.org\n> >Subject: RE: \"fatal: Not a git repository\" issued during 'make' from source\n> code\n> >\n> >Hi rsbecker,\n> >\n> >> -----Original Message-----\n> >> From: rsbecker@nexbridge.com \n> >> Sent: Friday, August 11, 2023 2:46 PM\n> >> To: Mun Johl ; 'Junio C Hamano' \n> >> Cc: git@vger.kernel.org\n> >> Subject: RE: \"fatal: Not a git repository\" issued during 'make' from\n> >> source code\n> >>\n> >> CAUTION: This email originated from outside of Western Digital. Do not\n> >> click on links or open attachments unless you recognize the sender and\n> know that\n> >the content is safe.\n> >>\n> >>\n> >> On Friday, August 11, 2023 5:15 PM, Mon Johl wrote:\n> >> >> On Friday, August 11, 2023 4:39 PM, Junio C Hamano wrote:\n> >> >> >Subject: Re: \"fatal: Not a git repository\" issued during 'make'\n> >> >> >from source\n> >> >> code\n> >> >> >\n> >> >> > writes:\n> >> >> >\n> >> >> >> On Friday, August 11, 2023 3:57 PM, Mun Johl wrote:\n> >> >> >>>I am new to git and am trying to compile git-2.41.0 on RHEL7.\n> >> >> >>>When I run\n> >> >> >> 'make\n> >> >> >>>prefix=/usr/local all doc', I get the following error:\n> >> >> >>>\n> >> >> >>>fatal: Not a git repository (or any parent up to mount point\n> >> >> >>>/tools)\n> >> >> >>>\n> >> >> >>>Which I infer means that I need to do the build within a git repo.\n> >> >> >>>Is\n> >> >> that\n> >> >> >> correct? Or\n> >> >> >>>have I missed some basic step in the build process?\n> >> >> >>\n> >> >> >> Yes, you must be in the cloned git repository in order to run\n> >> >> >> the\n> >> build.\n> >> >> >\n> >> >> >Shouldn't we be able to build out of a tarball?\n> >> >>\n> >> >> I don't get the impression he started with a tarball, so\n> >> >> subsequently sent the doc ref for that. Using just \"make\" is not\n> >> >> sufficient from a tarball.[Mun]\n> >> >\n> >> >[Mun] Thank you both for the information you have provided! It turns\n> >> >out I\n> >> did in fact\n> >> >start from the tar-ball \"git-2.41.0.tar.xz\" which I downloaded from\n> >> >https://mirrors.edge.kernel.org/pub/software/scm/git/ . And then I\n> >> >ran the\n> >> 'make'\n> >> >command. The process went something like this (basically identical\n> >> >to what\n> >> Junio\n> >> >documented):\n> >> >\n> >> >$ tar xf git-2.41.0.tar.xz\n> >> >$ cd git-2.41.0\n> >> >$ make prefix=/usr/local all doc\n> >> >\n> >> >And with the above 'make' command I got the fatal error.\n> >> >\n> >> >I consulted the Getting-Started-Installing-Git web page that rsbecker\n> >> referenced, and\n> >> >it basically matches the above--except it uses the 'make configure'\n> >> process. So I tried\n> >> >that method as well, but when I got to the 'make all doc info' step,\n> >> >I\n> >> again got the\n> >> >same fatal error.\n> >> >\n> >> >Due to some \"security precautions\", I am unable to use 'git clone\n> >> >https://git.kernel.org/pub/scm/git/git.git' to download the source code.\n> >> But I can try\n> >> >to figure out a workaround for that if that is my only option at this\n> >> >point\n> >> to\n> >> >successfully compile git.\n> >>\n> >> Did you run 'make configure' before using 'make prefix=/usr/local all\n> doc' ?\n> >\n> >[Mun] My apologies for not providing that data previously: Yes, I did run\n> 'make\n> >configure' prior to 'make prefix=/usr/local all doc'.\n> >\n> >Regards,\n> >\n> >--\n> >Mun\n\n"},{"id":"480674","messageId":"001001d9cf7f$96a62f50$c3f28df0$@nexbridge.com","threadId":"60106","inReplyTo":"PH0PR04MB8295B799ED69C91BBCCCED3B9C14A@PH0PR04MB8295.namprd04.prod.outlook.com","subject":"RE: \"fatal: Not a git repository\" issued during 'make' from source code","fromName":"","fromEmail":"rsbecker@nexbridge.com","sentAt":"2023-08-15T13:51:22Z","receivedAt":"2023-08-15T13:52:26Z","isPatch":false,"sender":{"key":"randall.becker@nexbridge.ca","avatar":"https://avatars.githubusercontent.com/u/28956764?v=4"},"body":"On Monday, August 14, 2023 9:15 PM, Mun Johl wrote:\n>> Rather than asking one line at a time, can you provide the complete\n>> log, input and output of the attempted operation, including the\n>> download and tar?[Mun]\n>\n>[Mun] I downloaded \"git-2.41.0.tar.xz\" from\n>https://mirrors.edge.kernel.org/pub/software/scm/git/ . Then I ran:\n>\n>$ unxz git-2.41.0.tar.xz\n>$ tar xvf git-2.41.0.tar\n>$ cd git-2.41.0\n>$ make configure\n>\n>The output of the above command was:\n>\n>GIT_VERSION = 2.41.0\n> GEN configure\n>\n>$ ./configure --prefix=/usr/local |& tee configure_20230814a_RHEL7.out\n// Output\n>is attached as \"configure_20230814a_RHEL7.out\"\n>$ make all doc |& tee make_20230814a_RHEL7.out // Output is attached\nas\n>\"make_20230814a_RHEL7.out\"\n>\n>I went over the output files but didn't notice anything to cause a fatal\nerror; although,\n>I do have some missing pkgs that I will work on retrieving and installing.\nRemember,\n>due to corporate security settings, I cannot simply to a 'yum install' of\nmissing pkgs.\n>\n>Thank you and regards,\n>\n>--\n>Mun\n>\n>> Thanks,\n>> Randall\n>>\n>> >-----Original Message-----\n>> >From: Mun Johl \n>> >Sent: Saturday, August 12, 2023 1:33 AM\n>> >To: rsbecker@nexbridge.com; 'Junio C Hamano' \n>> >Cc: git@vger.kernel.org\n>> >Subject: RE: \"fatal: Not a git repository\" issued during 'make' from\n>> >source\n>> code\n>> >\n>> >Hi rsbecker,\n>> >\n>> >> -----Original Message-----\n>> >> From: rsbecker@nexbridge.com \n>> >> Sent: Friday, August 11, 2023 2:46 PM\n>> >> To: Mun Johl ; 'Junio C Hamano'\n>> >> \n>> >> Cc: git@vger.kernel.org\n>> >> Subject: RE: \"fatal: Not a git repository\" issued during 'make'\n>> >> from source code\n>> >>\n>> >> CAUTION: This email originated from outside of Western Digital. Do\n>> >> not click on links or open attachments unless you recognize the\n>> >> sender and\n>> know that\n>> >the content is safe.\n>> >>\n>> >>\n>> >> On Friday, August 11, 2023 5:15 PM, Mon Johl wrote:\n>> >> >> On Friday, August 11, 2023 4:39 PM, Junio C Hamano wrote:\n>> >> >> >Subject: Re: \"fatal: Not a git repository\" issued during 'make'\n>> >> >> >from source\n>> >> >> code\n>> >> >> >\n>> >> >> > writes:\n>> >> >> >\n>> >> >> >> On Friday, August 11, 2023 3:57 PM, Mun Johl wrote:\n>> >> >> >>>I am new to git and am trying to compile git-2.41.0 on RHEL7.\n>> >> >> >>>When I run\n>> >> >> >> 'make\n>> >> >> >>>prefix=/usr/local all doc', I get the following error:\n>> >> >> >>>\n>> >> >> >>>fatal: Not a git repository (or any parent up to mount point\n>> >> >> >>>/tools)\n>> >> >> >>>\n>> >> >> >>>Which I infer means that I need to do the build within a git\nrepo.\n>> >> >> >>>Is\n>> >> >> that\n>> >> >> >> correct? Or\n>> >> >> >>>have I missed some basic step in the build process?\n>> >> >> >>\n>> >> >> >> Yes, you must be in the cloned git repository in order to run\n>> >> >> >> the\n>> >> build.\n>> >> >> >\n>> >> >> >Shouldn't we be able to build out of a tarball?\n>> >> >>\n>> >> >> I don't get the impression he started with a tarball, so\n>> >> >> subsequently sent the doc ref for that. Using just \"make\" is not\n>> >> >> sufficient from a tarball.[Mun]\n>> >> >\n>> >> >[Mun] Thank you both for the information you have provided! It\n>> >> >turns out I\n>> >> did in fact\n>> >> >start from the tar-ball \"git-2.41.0.tar.xz\" which I downloaded\n>> >> >from https://mirrors.edge.kernel.org/pub/software/scm/git/ . And\n>> >> >then I ran the\n>> >> 'make'\n>> >> >command. The process went something like this (basically\n>> >> >identical to what\n>> >> Junio\n>> >> >documented):\n>> >> >\n>> >> >$ tar xf git-2.41.0.tar.xz\n>> >> >$ cd git-2.41.0\n>> >> >$ make prefix=/usr/local all doc\n>> >> >\n>> >> >And with the above 'make' command I got the fatal error.\n>> >> >\n>> >> >I consulted the Getting-Started-Installing-Git web page that\n>> >> >rsbecker\n>> >> referenced, and\n>> >> >it basically matches the above--except it uses the 'make configure'\n>> >> process. So I tried\n>> >> >that method as well, but when I got to the 'make all doc info'\n>> >> >step, I\n>> >> again got the\n>> >> >same fatal error.\n>> >> >\n>> >> >Due to some \"security precautions\", I am unable to use 'git clone\n>> >> >https://git.kernel.org/pub/scm/git/git.git' to download the source\ncode.\n>> >> But I can try\n>> >> >to figure out a workaround for that if that is my only option at\n>> >> >this point\n>> >> to\n>> >> >successfully compile git.\n>> >>\n>> >> Did you run 'make configure' before using 'make prefix=/usr/local\n>> >> all\n>> doc' ?\n>> >\n>> >[Mun] My apologies for not providing that data previously: Yes, I did\n>> >run\n>> 'make\n>> >configure' prior to 'make prefix=/usr/local all doc'.\n\nSo this looks just like it is dependencies (like asciidoc), but the\nprocedure for configuring and running the git make looks correct. Yes?\n\n--Randall\n\n"},{"id":"480698","messageId":"SJ0PR04MB8289EAD6BDB5308778B89E979C15A@SJ0PR04MB8289.namprd04.prod.outlook.com","threadId":"60106","inReplyTo":"001001d9cf7f$96a62f50$c3f28df0$@nexbridge.com","subject":"RE: \"fatal: Not a git repository\" issued during 'make' from source code","fromName":"Mun Johl","fromEmail":"mun.johl@wdc.com","sentAt":"2023-08-16T00:19:04Z","receivedAt":"2023-08-16T00:20:01Z","isPatch":false,"sender":{"key":"mun.johl@wdc.com","avatar":null},"body":"Hi all,\n\n... Text Deleted ...\n\n> >> >[Mun] My apologies for not providing that data previously: Yes, I did\n> >> >run\n> >> 'make\n> >> >configure' prior to 'make prefix=/usr/local all doc'.\n> \n> So this looks just like it is dependencies (like asciidoc), but the\n> procedure for configuring and running the git make looks correct. Yes?\n\n[Mun] Yes.\n\nAs 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).\n\nNow I will move on to migrating our SVN repo to git (but apparently I am missing some Perl modules).\n\nI want to thank all of you for being so helpful!\n\nBest regards,\n\n-- \nMun\n\n\n> \n> --Randall\n\n"}]}