X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Message-ID:	<7CD0FF29D986456EBD660879815BAF24@cit.wayne.edu>
From:	"Lee Maschmeyer" <lee_maschmeyer AT wayne DOT edu>
To:	<cygwin AT cygwin DOT com>
References:	<7A40667E3D2C4AE49FC1811BB6945D13 AT cit DOT wayne DOT edu> <20080714203707 DOT GF24644 AT calimero DOT vinschen DOT de>
Subject:	Re: A path that's invalid on 1.7 but presumably valid on 1.5
Date:	Tue, 15 Jul 2008 10:49:35 -0400
MIME-Version:	1.0
X-Mailer:	Microsoft Outlook Express 6.00.2900.5512
X-Junkmail-Status:	score=10/50, host=mirapointmr2.wayne.edu
X-Junkmail-SD-Raw:	score=unknown, refid=str=0001.0A010203.487CB900.00E2,ss=1,fgs=0, ip=141.217.4.199, so=2007-10-30 19:00:17, dmn=5.4.3/2008-02-01
X-Junkmail-IWF:	false
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

From: "Corinna Vinschen"
To: <cygwin AT cygwin DOT com>
Sent: Monday, July 14, 2008 16:37
Subject: Re: A path that's invalid on 1.7 but presumably valid on 1.5


> On Jul 14 16:21, Lee Maschmeyer wrote:
>> The invalid path in question: //?/e:cygwin/usr/share/tcl8.4/init.tcl. 
>> This
>> is the path as supplied by tcl. To make it work, insert a / after the
>> colon: //?/e:/cygwin/usr/share/tcl8.4/init.tcl.
>
> Yes, that's right.  //?/e:cygwin is an invalid path.  I don't know
> where the path with the missing slash comes from, but this looks
> like an application or library bug.

Could it possibly be a path conversion error? Here's the error message; it 
looks possibly suspicious to me:

    //?/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

These are the 7 places where init.tcl is being searched. Notice that only 
the first has a slash after the colon. The second is the same as the first 
except with the slash missing, and the slash is missing after all of the 
other colons.

It's possible that whoever wrote the tcl (or whatever logic is involved) 
scripts just got lazy and quit including the slash, but that would be an 
explanation only if 1.5 didn't flag //?/e:cygwin as an error. I don't have a 
1.5 so can't check this.

At any rate, this isn't under my control as an end user. I wonder who needs 
to do what? This whole process worked without obvious error on 1.5.

Thanks very much,


-- 
Lee Maschmeyer
Computing Center Services
Computing and Information Technology
Wayne State University
Detroit, Michigan, USA 



--
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/

- Raw text -