git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: <rsbecker@nexbridge.com>
Cc: "'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 13:44:24 -0700	[thread overview]
Message-ID: <xmqqmsyxqpg7.fsf@gitster.g> (raw)
In-Reply-To: <xmqqr0o9qpon.fsf@gitster.g> (Junio C. Hamano's message of "Fri, 11 Aug 2023 13:39:20 -0700")

Junio C Hamano <gitster@pobox.com> writes:

> <rsbecker@nexbridge.com> writes:
>
>> 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.
>
> Shouldn't we be able to build out of a tarball?

In other words,

    $ mkdir -p /var/tmp/x
    $ cd /var/tmp/x
    $ wget http://www.kernel.org/pub/software/scm/git/testing/git-2.42.0.rc1.tar.xz
    $ tar xf git-2.42.0.rc1.tar.xz
    $ cd git-2.42.0.rc1
    $ make prefix=/var/tmp/local all doc
    $ sudo make prefix=/var/tmp/local install

is what I just did to make sure that a build from our tarball extract
does not require a git repository (it would be a bug to require one,
as it would make it impossible to bootstrap).

  reply	other threads:[~2023-08-11 20:44 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 [this message]
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=xmqqmsyxqpg7.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).