From: <rsbecker@nexbridge.com>
To: "'Mun Johl'" <Mun.Johl@wdc.com>, <git@vger.kernel.org>
Subject: RE: "fatal: Not a git repository" issued during 'make' from source code
Date: Fri, 11 Aug 2023 16:41:17 -0400 [thread overview]
Message-ID: <034c01d9cc94$30c14960$9243dc20$@nexbridge.com> (raw)
In-Reply-To: <SJ0PR04MB82893B315F130DCF181D78F49C10A@SJ0PR04MB8289.namprd04.prod.outlook.com>
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
next prev parent reply other threads:[~2023-08-11 20:41 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 [this message]
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
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='034c01d9cc94$30c14960$9243dc20$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=Mun.Johl@wdc.com \
--cc=git@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).