Re: Git building is borked

From: Anton Altaparmakov <aia21@cam.ac.uk>
Date: Mar 8, 2007, 15:07 UTC
Message-ID: <C5E8BD06-1404-403B-88D0-F24F386A14AF@cam.ac.uk>
In-Reply-To: <20070308145532.GA30674@spearce.org>

On 8 Mar 2007, at 14:55, Shawn O. Pearce wrote:

Show 9 quoted lines

> 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?

On my old workstation (Linux) which has the git git tree on it I tarred up the files in the git directory (not including the .git directory), then scp-ed the tar ball to my new workstation (OSX), untarred it there and tried to build git to boot strap...

Show 21 quoted lines

> 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.  ;-)

Ah, ok. I did not realize that released tar balls would be different to just tarring up the files...

That is fair enough. In the end I manage to boot strap myself by removing the git-gui stuff out of the main Makefile which allowed me to do make and sudo make install. Then I used the newly installed git to do a "git clone" of the git repository on kernel.org, then build and installed that which gave me git-gui as well.

I then deleted the old git directory I used for boot strapping.

Thanks for the quick response.

Best regards,

	Anton

-- 
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK
Linux NTFS maintainer, http://www.linux-ntfs.org/