Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
From: Chris Faylor <cgf@cygnus.com>
Date: Thu, 12 Oct 2000 10:28:45 -0400
To: Cygwin <cygwin@sources.redhat.com>
Subject: Re: Cygwin RCS Build Instructions (or sometimes ash does not like a.out)
Message-ID: <20001012102845.A20519@cygnus.com>
Reply-To: cygwin@sources.redhat.com
Mail-Followup-To: Cygwin <cygwin@sources.redhat.com>
References: <20001012102745.A1021@OLMY>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.6i
In-Reply-To: <20001012102745.A1021@OLMY>; from Jason.Tishler@dothill.com on Thu, Oct 12, 2000 at 10:27:45AM -0400

On Thu, Oct 12, 2000 at 10:27:45AM -0400, Jason Tishler wrote:
>I believe that I finally got to the bottom of why there are problems
>building RCS on Cygwin.  It boils down to an idiosyncrasy of ash which
>can be demonstrating by the following:
>
>    $ cd /tmp
>    $ cp /usr/bin/id.exe a.out
>    $ sh -c ./a.out
>    ./a.out: not found
>
>Hence, ash will not execute programs when their full path is specified
>and they don't end in ".exe".
>
>The above behavior was causing RCS's src/conf.sh to fail because it
>builds a.out files and attempts to run them via sh (i.e., ash) as
>"./a.out".  Hence, conf.sh would get confused and finally abort.

ash wants files to have the executable bit set.  Cygwin fakes this by looking
for files with specific extensions and setting the bit in that case.

'.out' is not one of the extensions.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com