Sorry for forgetting the cc!!!
Thank you so much for help, hope not to bore you all ;)
I think that I will go on studying git this way, and follow all the
improvements that were made along his history. I think that
asymptosis too gave me a good link, related to that bash script
implmentation.
Than
[+cc git@vger; let's keep this on the list; I'm not sure there's a lot
to be learned from fiddling with this old version, but if we're going
to do it, let's at least record our attempts for posterity]
On Thu, Mar 07, 2019 at 08:04:55PM +0100, Fabio Aiuto wrote:
> I made a directory "trial" and
On Wed, Mar 06, 2019 at 09:52:59PM +0100, Fabio Aiuto wrote:
> Found this error
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x00401628 in verify_hdr (hdr=0x0, size=32) at read-cache.c:192
> 192 if (hdr->signature != CACHE_SIGNATURE)
>
> when tracing on line
>
> static i
On Wed, Mar 06, 2019 at 03:39:11PM -0500, Santiago Torres wrote:
> I still find it somewhat astounding that it compiles with a modern
> toolchain after 15+ years. Many projects fail to do so (it's an
> understandably high bar to have).
I think the key thing is that Git has very few external depen
That was proably my bad.
I still find it somewhat astounding that it compiles with a modern
toolchain after 15+ years. Many projects fail to do so (it's an
understandably high bar to have).
I'm glad this is possible and you were able to do so (maybe you want to
share your experiences about it so
Found this error
Program received signal SIGSEGV, Segmentation fault.
0x00401628 in verify_hdr (hdr=0x0, size=32) at read-cache.c:192
192 if (hdr->signature != CACHE_SIGNATURE)
when tracing on line
static int verify_hdr(struct cache_header *hdr, unsigned long size)
{
SHA_CTX
Yes that's great.
Why somebody told me about a outdate toolchain when I started this
little thread about first git compiling? Sorry for my stupid question
but the you just resolved with that make override...
Maybe there's something I have to know?
Il giorno mer, 06/03/2019 alle 15.03 -0500, Jeff K
On Wed, Mar 06, 2019 at 08:58:40PM +0100, Fabio Aiuto wrote:
> Yes the fetch command wasn't written at that time, right? I didn't
> understand why should be better to work with the git code from github.
> There's something I misunderstood?
I just mean that it is an interesting fact that modern Gi
Il giorno mar, 05/03/2019 alle 14.15 -0500, Jeff King ha scritto:
> 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
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
> G
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..
Hi,
Fabio Aiuto wrote:
> What a pity, It would have been very useful for me, to debug around
> that simple version, to understand how everithing works.
Jeff King suggested how you can update the build command to get it
working. In general, I think people sometimes overthink what is
involved in
On Mon, Mar 04, 2019 at 09:19:52PM +0100, Fabio Aiuto wrote:
> What a pity, It would have been very useful for me, to debug around
> that simple version, to understand how everithing works.
To understand how Git works, it is a good idea to work through the "Git
Internals" chapter in the Git Book:
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-ca
It happens.
Something that I liked playing with to get myself a better handle of how
git works is using libgit2 and its python bindings. I find the codebase
a little bit smaller and its bindings to higher-level languages can help
you abstract the memory management and other low-level stuff that i
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 20
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
se
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: undefine
18 matches
Mail list logo
