git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Todd Zullinger <tmz@pobox.com>
To: Mun Johl <Mun.Johl@wdc.com>
Cc: git@vger.kernel.org
Subject: Re: "fatal: Not a git repository" issued during 'make' from source code
Date: Fri, 11 Aug 2023 20:54:15 -0400	[thread overview]
Message-ID: <ZNbYNxEfPYAB3ILb@pobox.com> (raw)
In-Reply-To: <SJ0PR04MB8289FF1D6BAC59833D922BA89C10A@SJ0PR04MB8289.namprd04.prod.outlook.com>

Hi,

Mun Johl wrote:
> I am new to git and am trying to compile git-2.41.0 on RHEL7.

This isn't a direct answer to the question (which Randall
and Junio have covered well), but if you're interested, I
build git-2.41.0 for RHEL/CentOS 7 (as well as newer
RHEL/Rocky/Alma and Fedora release) in the Fedora Copr
("Community projects"):

    https://copr.fedorainfracloud.org/coprs/g/git-maint/git/

I currently maintain the git package in Fedora and try to
ensure it always builds for all supported RHEL releases¹.

For RHEL/CentOS 7, the steps to install would be:

    yum install yum-plugin-copr
    yum copr enable @git-maint/git
    yum install git

The upside is that it's a current git build packaged the
same as the RHEL package.  The downside is that it updates
the RHEL package, which may not be acceptable in your
environment.

It's certainly a big jump from 1.8.3.1 to 2.41.0.  I had
forgotten how ancient the RHEL 7 git package was. :)

Alternately, building a git package for RHEL 7 from the
current Fedora git package is another option, if you'd
rather have an rpm to install on multiple hosts.

¹ I may not continue this due to Red Hat's recent decision
  to restrict access to RHEL source code, unfortunately.

-- 
Todd

  parent reply	other threads:[~2023-08-12  0:54 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
2023-08-12  5:30           ` Mun Johl
2023-08-12  0:54 ` Todd Zullinger [this message]
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=ZNbYNxEfPYAB3ILb@pobox.com \
    --to=tmz@pobox.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.
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).