X-Spam-Check-By: sourceware.org
Message-ID: <459F0303.40703@byu.net>
Date: Fri, 05 Jan 2007 19:01:39 -0700
From: Eric Blake <ebb9 AT byu DOT net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.9) Gecko/20061207 Thunderbird/1.5.0.9 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: upgrade advice for end users
References: <8188447 DOT post AT talk DOT nabble DOT com>
In-Reply-To: <8188447.post@talk.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to fschmidt on 1/5/2007 4:49 PM:
> Having just suffered through a cygwin upgrade, I would like to let other end
> users know what they need to do to get cygwin to work.
> 
> 1.  Create a new Windows System Environment variable called "SHELLOPTS" and
> set it to "igncr".  This makes bash handle CR/LF correctly.

There have been other reports that doing this makes scripts misbehave
because they aren't expecting to be interactive; one example
of this was problems using man.  So take the above advice with a grain of
salt.  Or do what I do - use binary files on binary mounts, and if I must
use text files, make sure they are on text mounts.  Setting SHELLOPTS is
somewhat of a last-ditch hack for the issue of CRLFs living on the wrong
mount style.

> 
> 2.  Replace /bin/make.exe with http://www.cmake.org/files/cygwin/make.exe . 
> The new version of make can't handle colons, so replace the new version with
> an old make that can handle colons.

Or wait patiently until the latest CVS version of make has stabilized on
path handling, and is released, at which point this workaround is no
longer needed.

> 
> I sincerely hope that either cygwin changes direction to be more Windows
> friendly, or that a cygwin fork is started in this direction.

You obviously haven't been reading the mail archives much in the last two
months.  Both of these issues have been talked to death, but so far, no
one has felt it necessary to fork cygwin over either of them.

- --
Don't work too hard, make some time for fun as well!

Eric Blake             ebb9 AT byu DOT net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFnwMC84KuGfSFAYARAt1tAJ423uE31NAnorjqL25hw1UUzILasQCfYuL3
Ej/ok84F7DofIaFnyIKQaLo=
=n12A
-----END PGP SIGNATURE-----

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