From: <rsbecker@nexbridge.com>
To: "'Junio C Hamano'" <gitster@pobox.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 17:51:20 -0400 [thread overview]
Message-ID: <036801d9cc9d$fa5c3920$ef14ab60$@nexbridge.com> (raw)
In-Reply-To: <xmqqr0o9p7vj.fsf@gitster.g>
>-----Original Message-----
>From: Junio C Hamano <gitster@pobox.com>
On Friday, August 11, 2023 5:49 PM, Junio C Hamano wrote:
>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
>
><rsbecker@nexbridge.com> writes:
>
>> Did you run 'make configure' before using 'make prefix=/usr/local all
doc' ?
>
>A tarball release ships with configure (built out of configure.in)
included, so that
>should not be necessary.
Thanks. I don't usually build from a tarball. However, the OP did not
indicate that configure was run either.
next prev parent reply other threads:[~2023-08-11 21:51 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 [this message]
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='036801d9cc9d$fa5c3920$ef14ab60$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=Mun.Johl@wdc.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).