git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Fabio Aiuto <polinice83@libero.it>
Cc: git@vger.kernel.org
Subject: Re: Can't build first git commit
Date: Tue, 5 Mar 2019 14:15:19 -0500	[thread overview]
Message-ID: <20190305191519.GA12791@sigill.intra.peff.net> (raw)
In-Reply-To: <20190304204007.GA32691@sigill.intra.peff.net>

On Mon, Mar 04, 2019 at 03:40:07PM -0500, Jeff King wrote:

> You can patch the Makefile, or just override it like:
> 
>   make LIBS='-lcrypto -lz'
> 
> which builds for me on current Debian unstable. I don't think you can
> actually fetch with that old build, but I used periodically check that
> Git v1.0 can fetch happily from GitHub. I haven't in a while, so let me
> know if you try it and it doesn't work. ;)

I just tried this, and it does indeed work. I had to build v1.0.0 with

  make NO_OPENSSL=Nope

I think the issue is that some old code embedded openssl's BIGNUM in a
struct, and later versions of openssl stopped publicly defining the
types.

I was able to clone git://github.com/git/git with the result, though of
course it chokes no the sha1collisiondetection submodule. You can still
use "git log", though, and checkout older commits.

-Peff

  parent reply	other threads:[~2019-03-05 19:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-04 19:58 Can't build first git commit Fabio Aiuto
2019-03-04 20:10 ` Santiago Torres
2019-03-04 20:19   ` Fabio Aiuto
2019-03-04 20:22     ` Santiago Torres
2019-03-04 21:48     ` asymptosis
2019-03-04 22:25     ` Jonathan Nieder
2019-03-04 20:40 ` Jeff King
2019-03-05 18:42   ` Fabio Aiuto
2019-03-05 19:15   ` Jeff King [this message]
2019-03-06 19:58     ` Fabio Aiuto
2019-03-06 20:03       ` Jeff King
2019-03-06 20:19         ` Fabio Aiuto
2019-03-06 20:39           ` Santiago Torres
2019-03-06 21:54             ` Jeff King
2019-03-06 20:52         ` Fabio Aiuto
2019-03-06 21:57           ` Jeff King
     [not found]             ` <1551985495.1606.1.camel@libero.it>
2019-03-07 19:41               ` Jeff King
2019-03-07 20:07                 ` Fabio Aiuto

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190305191519.GA12791@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=polinice83@libero.it \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).