From: "Dirk Süsserott" <newsletter@dirk.my1.cc>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "Dirk Süsserott" <newsletter@dirk.my1.cc>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: msysGit and SCons: broken?
Date: Sat, 15 Aug 2009 16:04:28 +0200 [thread overview]
Message-ID: <4A86C06C.3060409@dirk.my1.cc> (raw)
In-Reply-To: <alpine.DEB.1.00.0908132353380.8306@pacific.mpi-cbg.de>
Am 13.08.2009 23:54 schrieb Johannes Schindelin:
> Hi,
>
> On Thu, 13 Aug 2009, Dirk Süsserott wrote:
>
...
>> If someone had the same or a similar problem: I tracked it down and
>> found a solution. The problem was that I tried to run a Windows program
>> from git-bash. The Windows program then faces the bash's $PATH with a
>> different separator (':' vs. ';') and a different root directory ('/c/'
>> vs. 'C:/').
>
> I cannot believe that. I actually run a Windows program very often, from
> Git Bash, and PATH is correctly converted all the time.
>
> Ciao,
> Dscho
Hmm, I wrote a simple "hello $PATH" and it actually DID print the path
in Windows' flavour when started from Git Bash, like you said. Dunno why
ActivePython ceased to do so as well... Probably I confused my machine
by extending PATH in Windows and .bashrc with different PATHs in
different order. Or ActivePython is somehow "zickig" (what's that in
english? :-)). However, now it works for me and as SCons is the only
tool that failed, I see no further need for investigation.
Btw., I started scons from Git Bash with
cmd //c C:/Python24/Scripts/scons.bat "$@"
Maybe that's a problem, but I don't care any longer.
Dirk
prev parent reply other threads:[~2009-08-15 14:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-03 18:19 msysGit and SCons: broken? Dirk Süsserott
2009-08-03 22:13 ` Johannes Schindelin
2009-08-06 19:45 ` Dirk Süsserott
2009-08-13 19:32 ` Dirk Süsserott
2009-08-13 21:54 ` Johannes Schindelin
2009-08-15 14:04 ` Dirk Süsserott [this message]
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=4A86C06C.3060409@dirk.my1.cc \
--to=newsletter@dirk.my1.cc \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.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).