From: "Shawn O. Pearce" <spearce@spearce.org>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: git@vger.kernel.org
Subject: Re: Git building is borked
Date: Thu, 8 Mar 2007 09:55:32 -0500 [thread overview]
Message-ID: <20070308145532.GA30674@spearce.org> (raw)
In-Reply-To: <F0177878-0A2B-43B0-9838-E032FB3A0A58@cam.ac.uk>
Anton Altaparmakov <aia21@cam.ac.uk> wrote:
> But now I put the git-gui mentions back into the Makefile and tried
> again it still fails. Looking at it closer it actually requires me
> to compile within a checked out git tree, i.e. including the .git
> directory and all its contents! That seems even weirder than
> requiring git to be installed in the first place...
What version of Git specifically are you building with? How did
you obtain these source files?
Release tarballs of Git contain a git-gui/credits file that makes
CREDITS-GEN avoid invoking the not-yet-existing Git. Building
git-gui without this file does require not only a working Git
installation, but also the git-gui object database. Both of these
are readily available on a Git hacker's system, and on any system
that is attempting to create a release tarball.
There are other files included in the release tarballs (version,
git-gui/version) that are also required to get a correct build when
you don't have Git installed, or are missing its object database.
Having these missing does not stop the build process, but it does
make the output of `git version` and `git gui version` relatively
useless.
So you need to be bootstrapping from a released *.tar.{gz,bz2},
which can be found here:
http://www.kernel.org/pub/software/scm/git/
Sadly, simply downloading the source files from a random gitweb
doesn't work anymore. Yes, I know, my fault. ;-)
--
Shawn.
next prev parent reply other threads:[~2007-03-08 14:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 10:21 Git building is borked Anton Altaparmakov
2007-03-08 10:29 ` Anton Altaparmakov
2007-03-08 14:55 ` Shawn O. Pearce [this message]
2007-03-08 15:07 ` Anton Altaparmakov
2007-03-08 15:13 ` Shawn O. Pearce
2007-03-08 15:19 ` Anton Altaparmakov
2007-03-08 15:10 ` Anton Altaparmakov
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=20070308145532.GA30674@spearce.org \
--to=spearce@spearce.org \
--cc=aia21@cam.ac.uk \
--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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox