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 12:56:28 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0610011255030.3952@g5.osdl.org> (raw)
In-Reply-To: <7vlknz27qm.fsf@assigned-by-dhcp.cox.net>
On Sun, 1 Oct 2006, Junio C Hamano wrote:
>
> Everybody hated the perl crud, so we removed Git.xs and is not
> even part of the source anymore.
>
> This is a symptom that Git.c leftover from an earlier build was
> in the working tree. Could you try running "rm -f perl/Git.c"
> before building and see if it helps?
Nope.
Then I just get
make[1]: Entering directory `/home/torvalds/git/perl'
Running Mkbootstrap for Git ()
chmod 644 Git.bs
rm -f blib/arch/auto/Git/Git.so
gcc -shared -L/usr/local/lib Git.o -o blib/arch/auto/Git/Git.so \
\
gcc: Git.o: No such file or directory
gcc: no input files
instead.
If that file isn't even supposed to _exist_, then why do we have build
rules etc crap to do all this? It sounds like the makefiles are broken.
Linus
next prev parent reply other threads:[~2006-10-01 19:56 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
2006-10-01 18:47 ` Junio C Hamano
2006-10-01 19:56 ` Linus Torvalds [this message]
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.0610011255030.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).