From: Linus Torvalds <torvalds@osdl.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: What will happen to git.git in the near future
Date: Sun, 1 Oct 2006 11:38:06 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0610011132040.3952@g5.osdl.org> (raw)
In-Reply-To: <7vd59c2vev.fsf@assigned-by-dhcp.cox.net>
On Sun, 1 Oct 2006, Junio C Hamano wrote:
>
> I've tagged the tip of the master as v1.4.3-rc1 tonight, after
> merging things that I listed in the message last week to be
> merged from "next".
>
> Have fun.
I hate that perl crud.
...
make -C perl
make[1]: Entering directory `/home/torvalds/git/perl'
cp private-Error.pm blib/lib/Error.pm
cp Git.pm blib/lib/Git.pm
gcc -c -D_REENTRANT -D_GNU_SOURCE -fno-strict-aliasing -pipe -Wdeclaration-after-statement -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/gdbm -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -DVERSION=\"0.01\" -DXS_VERSION=\"0.01\" -fPIC "-I/usr/lib/perl5/5.8.8/ppc-linux-thread-multi/CORE" Git.c
In file included from Git.xs:8:
../cache.h:6:10: error: #include expects "FILENAME" or <FILENAME>
Git.xs: In function 'XS_Git_xs_version':
Git.xs:62: error: 'GIT_VERSION' undeclared (first use in this function)
Git.xs:62: error: (Each undeclared identifier is reported only once
Git.xs:62: error: for each function it appears in.)
make[1]: *** [Git.o] Error 1
make[1]: Leaving directory `/home/torvalds/git/perl'
make: *** [all] Error 2
I don't like how git now doesn't compile just out of the box on a
perfectly regular FC5 box.
The whole Git.xs stuff has been buggered from the very beginning, at some
point somebody needs to just admit it.
Please?
And how come does this actually work for anybody else? I've got PPC_SHA1
defined, but I don't see what the difference is..
Linus
next prev parent reply other threads:[~2006-10-01 18:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-24 10:37 What will happen to git.git in the near future Junio C Hamano
2006-09-24 11:04 ` Petr Baudis
2006-09-24 16:56 ` Rene Scharfe
2006-09-24 18:33 ` Johannes Schindelin
2006-09-24 18:42 ` A Large Angry SCM
2006-10-01 10:16 ` Junio C Hamano
2006-10-01 18:38 ` Linus Torvalds [this message]
2006-10-01 18:47 ` Junio C Hamano
2006-10-01 19:56 ` Linus Torvalds
2006-10-01 18:53 ` Johannes Schindelin
2006-10-01 19:57 ` Linus Torvalds
2006-10-01 20:11 ` Johannes Schindelin
2006-10-01 20:23 ` Linus Torvalds
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=Pine.LNX.4.64.0610011132040.3952@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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 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 NNTP newsgroup(s).