Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Message-ID: <426B7FB8.4070004@x-ray.at>
Date: Sun, 24 Apr 2005 13:15:04 +0200
From: Reini Urban <rurban AT x-ray DOT at>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.8b) Gecko/20050217
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: bash was: can not run OPUS MAKE
References: <BAY10-F359FACDF4E8A712EE1F703E92B0 AT phx DOT gbl> <6 DOT 2 DOT 1 DOT 2 DOT 0 DOT 20050420135158 DOT 08700910 AT pop DOT prospeed DOT net> <42673DF8 DOT 4020005 AT x-ray DOT at> <20050422030853 DOT GA16112 AT trixie DOT casa DOT cgf DOT cx>
In-Reply-To: <20050422030853.GA16112@trixie.casa.cgf.cx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Christopher Faylor schrieb:
> On Thu, Apr 21, 2005 at 07:45:28AM +0200, Reini Urban wrote:
> 
>>The problem is bash related.
>>
>>lame.exe invocation or mencoder.exe (probably arg parsing) also fails 
>>with a 1.5.15s-20050413 and latest bash-2.05b.0(1)-release (2.05b-17), 
>>but I haven't found time to debug it.
>>Reproduced with cygwin-1.5.15 release also.
> 
> 
> This is a disappointingly vague message.  I'm not sure what you hoped to
> gain from sending it since it contains no details or, AFAICT, any useful
> information other than "I had a problem" which, despite your previous
> high-quality contributions to this mailing list, does not preclude cockpit
> errors.
> 
> In any event, I have downloaded lame from a web site in France and it seems
> to behave just fine with bash.  I installed lame to /usr/bin and tried mounting
> /usr/bin with and without the -X directive, just in case that was a factor.
> 
> lame worked fine in both cases.
> 
> 
>>Passing the same cmdlines to cmd.exe or within cygwin tcsh or zsh do 
>>work fine. With the previous bash also.
> 
> 
> So, don't keep us in suspense.  What were the command lines that caused the
> problem?

Sorry, but I was in a hurry then:

The problem was not related to bash, but to my testing of the mount -X 
switch for /usr/local/bin (cygexec) which caused all my non-cygwin exes 
there to fail.

-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/
http://phpwiki.org/

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