Git development
 help / color / mirror / Atom feed
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 10:13:02 -0500	[thread overview]
Message-ID: <20070308151302.GC30674@spearce.org> (raw)
In-Reply-To: <C5E8BD06-1404-403B-88D0-F24F386A14AF@cam.ac.uk>

Anton Altaparmakov <aia21@cam.ac.uk> wrote:
> On 8 Mar 2007, at 14:55, Shawn O. Pearce wrote:
> >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...

Since you solved your problem, this is more for the list archives
than anything:

Use `make dist` instead.  It uses your currently installed Git
to generate a tarball from the revision in HEAD, then appends in
the 4 critical files.  I use this all of the time (almost daily,
or close to it) to do builds of Git on Cygwin and Solaris 9.
In both cases I am building without `git` (or .git) available,
and am relying on just the output of `make dist`.
 
-- 
Shawn.

  reply	other threads:[~2007-03-08 15:13 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
2007-03-08 15:07     ` Anton Altaparmakov
2007-03-08 15:13       ` Shawn O. Pearce [this message]
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=20070308151302.GC30674@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