From: Fabio Aiuto <polinice83@libero.it>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: Can't build first git commit
Date: Tue, 05 Mar 2019 19:42:54 +0100 [thread overview]
Message-ID: <1551811374.1607.3.camel@libero.it> (raw)
In-Reply-To: <20190304204007.GA32691@sigill.intra.peff.net>
Thank you Jeff I'll have news within few days!!!
Il giorno lun, 04/03/2019 alle 15.40 -0500, Jeff King ha scritto:
> On Mon, Mar 04, 2019 at 08:58:37PM +0100, Fabio Aiuto wrote:
>
> > I'm trying to build first commit of git made by Linus. I mean the
> > one
> > named e83c5163316f89bfbde7d9ab23... (I think this is enough).
> > But at building stage i have the following error:
> >
> > make all
> > gcc -g -o update-cache update-cache.o read-cache.o -lssl
> > /usr/bin/ld: update-cache.o: undefined reference to symbol
> > 'SHA1_Update@@OPENSSL_1_1_0'
>
> The sha1 routines are in libcrypto. See 3be4b61aa4 (Link with
> -lcrypto
> instead of -lssl when using openssl libraries., 2005-05-10). I also
> needed -lz. See 9426167765 (Add "-lz" to link line to get in zlib.,
> 2005-04-08).
>
> 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. ;)
>
> -Peff
next prev parent reply other threads:[~2019-03-05 18:42 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 [this message]
2019-03-05 19:15 ` Jeff King
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1551811374.1607.3.camel@libero.it \
--to=polinice83@libero.it \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.