This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Thanks. Re: Broken Bash 2.05? a configure can't find /bin/sh

On Wed, Apr 25, 2001 at 05:37:21PM -0700, Dennis Wilson wrote:
>The explanation is great. I can work around this. I just thought I had done
>something wrong on my
>upgrade and was preparing to reinstall.

Actually, as I noted, the explanation did not really explain your problem.
It appears that there *is* something wrong with your installation if you
don't have a /bin/sh.

>Cygwin is a GREAT way for a unix person to get along with windows. I hope
>you guys can continue.

Well, cygwin seems to be gaining in popularity both without and within
(despite a few annoying nay-sayers) Red Hat so it looks like we'll be
hear for a while.


>----- Original Message -----
>From: "Troy Noble" <>
>To: "'Dennis Wilson'" <>; <>
>Sent: Wednesday, April 25, 2001 7:59 AM
>Subject: RE: Broken Bash 2.05? a configure can't find /bin/sh
>> bash doesn't get installed as /bin/sh, it gets installed as /bin/bash.
>> The "ash" package (a Bourne shell clone) is the one that actually gets
>> installed as /bin/sh.  So if you didn't install ash*.tar.gz, you've
>> likely not got a /bin/sh.
>> What we've done to get around this is install the "bash" package, but
>> not the "ash" package, and then we:
>> cp -p /bin/bash.exe /bin/sh.exe
>> and that ensures that we are always running bash and that /bin/sh
>> is always there.  We've standardized on BASH for our purposes here,
>> so this is acceptable practice for our environment.
>> YMMV.
>> Troy
>> -----Original Message-----
>> From: Dennis Wilson []
>> Sent: Tuesday, April 24, 2001 8:08 PM
>> To:
>> Subject: Broken Bash 2.05? a configure can't find /bin/sh
>> I ungraded my cygwin on my Win2k system. It now can't find sh.
>> I did not do anything but run the setup and accept the packages that
>> to be upgraded.
>> I was working on building tcl and when I went back into the directory to
>> the configure script I got the following message.
>> $ ./configure --enable-gcc
>> bin/bash .configure: bad interpreter: no such file or directory.
>> What appears to be going on is that the pathing has changed and /bin/sh is
>> no longer valid.
>> Any ideas??

Want to unsubscribe from this list?
Check out:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]