Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Message-ID:	<3F8AD3CD.6050502@trivee.org>
Date:	Mon, 13 Oct 2003 09:33:17 -0700
From:	Vladimir Vysotsky <trivee AT trivee DOT org>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20030916
X-Accept-Language:	en-us, en, ru
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Possible bug in text/binary mode handling in cygwin1.dll version1.5
References:	<5Csi/8Wu7mqJ092yn AT world DOT std DOT com>
In-Reply-To:	<5Csi/8Wu7mqJ092yn@world.std.com>

Jeff wrote:
> Vlad wrote:
>>In other words, text mode is ignored if Windows-style path is
>>specified.
> I noticed this same behavior and posted on it a bit earlier this month. 

Jeff, I've noticed your email after I've posted mine :) I believe it's
the same problem.

> $ command -option `cygpath c:\whereever\whatever`

This is a great suggestion. The toolkit I'm dealing with uses an
environment variable TOOLKIT_ROOT, which used to be specified
Windows-style. Converting it to unix path seems to fix the compilation
problem.

I still wish cygwin1.dll would take care of this automatically.

Thanks,
Vlad


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