X-Recipient: archive-cygwin@delorie.com
X-Spam-Check-By: sourceware.org
Date: Tue, 22 Jul 2008 15:56:43 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: 1.7.0-19: Still unexplained path problems
Message-ID: <20080722135643.GA21785@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <6086F48CE8E1479DB51E00035DFD5B14@cit.wayne.edu> <20080722094517.GF5251@calimero.vinschen.de> <4885CCBE.8090305@byu.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4885CCBE.8090305@byu.net>
User-Agent: Mutt/1.5.16 (2007-06-09)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On Jul 22 06:04, Eric Blake wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> According to Corinna Vinschen on 7/22/2008 3:45 AM:
> |> application-specific initialization failed: Can't find a usable
> init.tcl in
> |> the following directories:
> |>    //?/E:/cygwin/share/tcl8.4 //?/E:cygwin/share/tcl8.4
> |> //?/E:cygwin/usr/share/tcl8.4 //?/E:share/tcl8.4 //?/E:cygwin/library 
> //?/E
> |> :library //?/E:../tcl8.4.1/library
> |
> | As I said in my first reply, this is likely a problem in autogen, TCL or
> | brltty.
>
> I can rule out autogen and brltty.  I can't build git on 1.7.0 either, for
> the same reason, for several months now.  Something in tcl is not very
> happy with 1.7.0.  And since I'm relegated to building git under 1.5.x, I
> can't test git's claim to using IPv6.

Can you create an strace of a testcase (building git or something)
which shows where and how the paths are generated?  Maybe we can
workaround this in Cygwin itself by tweaking paths missing a / or \
after the colon...

> Not to mention that cygwin's tcl is very old - I had to apply a patch to
> git to work around the fact that cygwin's tcl doesn't know how to redirect
> stderr, when compared with all the other distros that have a more modern
> version.

Yeah.  It would be cool if we could get a new tcl version at one point.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

