Message-ID: <55311.99.237.216.211.1246850167.squirrel@www.sidefx.com>
In-Reply-To: <4A50E796.80409@verizon.net>
References: <4A50437D.10808@gmail.com> <4A504898.6080108@gmail.com>     <4A50E796.80409@verizon.net>
Date: Sun, 5 Jul 2009 23:16:07 -0400 (EDT)
Subject: Re: fresh 1.7, bash fails with STATUS_ACCESS_VIOLATION
From: "Edward Lam" <edward@sidefx.com>
To: cygwin@cygwin.com
User-Agent: SquirrelMail/1.4.9a
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Sun, July 5, 2009 13:49, Jerry DeLisle wrote:
> Fresh install still broken with backing down one rev on bash and using
> libreadline6.

I ran into this Friday as others have noted. The thing that caught me was
that the postinstall scripts in the installer rely on a working bash. Once
I had a broken fresh cygwin install, simply backing down one rev of bash
didn't help because the postinstall scripts of the OTHER packages that are
already installed need to be re-run since they didn't run in the first
place.

Here's what I did (roughly) in order to get a working cygwin 1.7
installation:

- Backup any data I wanted to keep under c:/cygwin/home/username
- Removed c:/cygwin and all previously downloaded files by setup-1.7.exe
- Launched setup-1.7.exe
- Specify additional packages that I wanted to install
- Changed the version of bash down to 3.2.49-22
- Added libreadline6 package
- Now install the changes

Regards,
-Edward


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