From: Junio C Hamano <gitster@pobox.com>
To: Mun Johl <Mun.Johl@wdc.com>
Cc: "rsbecker@nexbridge.com" <rsbecker@nexbridge.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: "fatal: Not a git repository" issued during 'make' from source code
Date: Fri, 11 Aug 2023 14:46:29 -0700 [thread overview]
Message-ID: <xmqqv8dlp80a.fsf@gitster.g> (raw)
In-Reply-To: <SJ0PR04MB82892A7EB350531DBE4701BA9C10A@SJ0PR04MB8289.namprd04.prod.outlook.com> (Mun Johl's message of "Fri, 11 Aug 2023 21:15:22 +0000")
Mun Johl <Mun.Johl@wdc.com> writes:
> 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.
If building from tarball extract fails with "not a git repository"
there is something very wrong with what you are doing, and we do not
know what it is.
Most likely cause new folks fail to build from the source is lack of
necessary development libraries and packages that need to be
installed in their build environment, but I am reasonably certain
that if a tarball extract build is failing due to their environment,
build in a clone of the source repository would fail for exactly the
same reason.
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
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 [this message]
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=xmqqv8dlp80a.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Mun.Johl@wdc.com \
--cc=git@vger.kernel.org \
--cc=rsbecker@nexbridge.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 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).