From: Steffen Prohaska <prohaska@zib.de>
To: "Shawn O. Pearce" <spearce@spearce.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Marius Storm-Olsen <marius@trolltech.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: msysgit: does git gui work?
Date: Thu, 9 Aug 2007 23:23:15 +0200 [thread overview]
Message-ID: <E886F099-5E9F-4785-A560-F9AAAA4E4C1F@zib.de> (raw)
In-Reply-To: <3CD6111C-13B5-444C-A28C-A7445C8A199B@zib.de>
On Aug 9, 2007, at 9:24 AM, Steffen Prohaska wrote:
> Does 'git gui' work for you in msysgit?
>
> I get
>
> Invalid command name "git-version"
> while executing
> "git-version >= 1.5.3"
> (in namespace eval "::blame" script line 36)
> [...]
>
> with msysgit (v1.5.3-rc2-690-g8ca1f6a)
Ok this is a bit complex but simple to solve: I created a
symlink from tclsh84.exe to tclsh.exe, that is
cd /mingw/bin
ln -s tclsh84.exe tclsh.exe
And than run
make install
[
offtopic:
I also hacked the Makefile to set GIT_VERSION to normal
version number, like 99.9, because git gui complained that
it failed to parse the version number.
I'll look into this later.
]
Now the long story.
mingw only contains tclsh84 but not tclsh. This causes
the Makefile in git-gui to fail on the creation of
lib/tclIndex. Therefore git gui decides to take the slow
path of sourcing the files in lib explicitly but this failes
because they are sourced before git-version is defined.
Therefore blame.tcl reports the error mentioned above.
Johannes (or someone else from the msysgit team),
We should modify mingw to contain the symlink to tclsh.
Or something similar, at least 'tclsh' should be there.
Shawn,
The fallback mechanism of sourcing files from lib is broken.
Either git-version must be defined before sourcing them, or
the auto_index must always work.
Steffen
next prev parent reply other threads:[~2007-08-09 21:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 7:24 msysgit: does git gui work? Steffen Prohaska
2007-08-09 21:23 ` Steffen Prohaska [this message]
2007-08-10 5:31 ` Shawn O. Pearce
2007-08-10 7:03 ` Steffen Prohaska
2007-08-10 7:38 ` Steffen Prohaska
2007-08-10 7:47 ` Marius Storm-Olsen
2007-08-10 10:26 ` Steffen Prohaska
2007-08-10 10:16 ` Johannes Schindelin
2007-08-10 10:51 ` Steffen Prohaska
2007-08-10 12:13 ` Johannes Schindelin
2007-08-10 13:48 ` Steffen Prohaska
2007-08-10 13:53 ` Johannes Schindelin
2007-08-10 16:47 ` Steffen Prohaska
2007-08-10 11:40 ` Alex Riesen
2007-08-11 6:10 ` Dmitry Kakurin
2007-08-11 8:40 ` Alex Riesen
-- strict thread matches above, loose matches on Subject: below --
2007-08-10 22:00 Brett Schwarz
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=E886F099-5E9F-4785-A560-F9AAAA4E4C1F@zib.de \
--to=prohaska@zib.de \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=marius@trolltech.com \
--cc=spearce@spearce.org \
/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).