Date: Sat, 30 May 2009 21:53:27 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin postinstall scripts / bash [ ] syntax fails on Win 2003 	x64  / Xen
Message-ID: <20090531015327.GB23854@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <20090530181925.4hkr5kpty0aogkgs@webmail.integrasphere.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20090530181925.4hkr5kpty0aogkgs@webmail.integrasphere.com>
User-Agent: Mutt/1.5.19 (2009-01-05)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Sat, May 30, 2009 at 06:19:25PM -0500, dsp435@integrasphere.com wrote:
>First time writing to this list, forgive me if this is redundant but I
>have spent many hours researching this issue and while it seems to be
>at least a known issue, I can't find any evidence it has been
>addressed.
>
>The best thing I can do is point you to this post, it is quite telling:
>http://markmail.org/message/owy3x7pf6oywdx5e#query:+page:1+mid:owy3x7pf6oywdx5e+state:results
>
>I am not using "KVM", but I am using Windows 2003 x64 on Xen, and I am
>having the same issue.  Cygwin fails to run the postinstall scripts,
>and this leaves the environment all but unusable.  It comes down to the
>fact that bash cannot execute the "test" or "[ x ]" syntax without
>throwing a segmentation fault.  Running [ 1 ] at the bash prompt
>immediately reproduces the bug.  The bash prompt can be loaded, but non
>of the startup scripts are executed and I just get a bash-3.2$ prompt
>in /usr/bin.
>
>The people who posted at the above link wrote a patch that supposedly
>solved the problem, but there is no way for a normal user to try this
>without a compiler and it doesn't appear to be in the release Cygwin
>code yet.  I also tried the Cygwin 1.7 beta and have the same problem.

I didn't see any Cygwin patch there.   AFAICT, someone changed kvm.

If there is a Cygwin patch you'll need to be more explicit.

cgf

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