From: Fabio Aiuto <polinice83@libero.it>
To: Santiago Torres <santiago@nyu.edu>
Cc: git@vger.kernel.org
Subject: Re: Can't build first git commit
Date: Mon, 04 Mar 2019 21:19:52 +0100 [thread overview]
Message-ID: <1551730792.4573.1.camel@libero.it> (raw)
In-Reply-To: <20190304201011.j7dopqp6ug66ccum@LykOS.localdomain>
What a pity, It would have been very useful for me, to debug around
that simple version, to understand how everithing works.
Thank you Santiago.
Fabio.
Il giorno lun, 04/03/2019 alle 15.10 -0500, Santiago Torres ha scritto:
> This commit is about 14 years old:
>
> Date: Thu Apr 7 15:13:13 2005 -0700
>
> Unless you have a toolchain from around that time, I'd be very
> surprised
> if things build. Notably, there you're having an issue with the
> symbols
> that lssl is exposing (I suspect you're not even using the openssl
> 1.0.0
> series anymore.
>
> Thanks,
> -Santiago.
>
> On Mon, Mar 04, 2019 at 08:58:37PM +0100, Fabio Aiuto wrote:
> > Hi to all,
> >
> > 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'
> > //usr/lib/i386-linux-gnu/libcrypto.so.1.1: error adding symbols:
> > DSO
> > missing from command line
> > collect2: error: ld returned 1 exit status
> > make: *** [update-cache] Errore 1
> > Makefile:16: set di istruzioni per l'obiettivo "update-cache" non
> > riuscito
> >
> > I run a debian stretch on my machine. Could anyone help me?
> > Thanks in advance.
> > Fabio.
> >
next prev parent reply other threads:[~2019-03-04 20:19 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 [this message]
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
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=1551730792.4573.1.camel@libero.it \
--to=polinice83@libero.it \
--cc=git@vger.kernel.org \
--cc=santiago@nyu.edu \
/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).