From: Mun Johl <Mun.Johl@wdc.com>
To: "rsbecker@nexbridge.com" <rsbecker@nexbridge.com>,
'Junio C Hamano' <gitster@pobox.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: RE: "fatal: Not a git repository" issued during 'make' from source code
Date: Wed, 16 Aug 2023 00:19:04 +0000 [thread overview]
Message-ID: <SJ0PR04MB8289EAD6BDB5308778B89E979C15A@SJ0PR04MB8289.namprd04.prod.outlook.com> (raw)
In-Reply-To: <001001d9cf7f$96a62f50$c3f28df0$@nexbridge.com>
Hi all,
... Text Deleted ...
> >> >[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?
[Mun] Yes.
As 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).
Now I will move on to migrating our SVN repo to git (but apparently I am missing some Perl modules).
I want to thank all of you for being so helpful!
Best regards,
--
Mun
>
> --Randall
next prev parent reply other threads:[~2023-08-16 0:20 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 [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SJ0PR04MB8289EAD6BDB5308778B89E979C15A@SJ0PR04MB8289.namprd04.prod.outlook.com \
--to=mun.johl@wdc.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).