www.delorie.com/archives/browse.cgi | search |
Delivered-To: | listarch-cygwin AT sourceware DOT cygnus DOT com |
Mailing-List: | contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm |
Sender: | cygwin-owner AT sourceware DOT cygnus DOT com |
Delivered-To: | mailing list cygwin AT sourceware DOT cygnus DOT com |
Message-ID: | <36C4874D.71585466@paul.rutgers.edu> |
Date: | Fri, 12 Feb 1999 14:55:57 -0500 |
From: | Anil K Ruia <ruia AT paul DOT rutgers DOT edu> |
Organization: | Rutgers University |
X-Mailer: | Mozilla 4.5 [en] (Win98; I) |
X-Accept-Language: | en |
MIME-Version: | 1.0 |
To: | cygwin AT sourceware DOT cygnus DOT com |
Subject: | Re: Here documents in ash shell scripts mess up stdin on 9x |
References: | <36c4737f DOT 46513371 AT mail DOT goodnet DOT com> |
Thanx Mike for diagnosing the cause of the problem. I had been having this problem on Win98 with B20.1 also and hadn't been able to find a solution. I just made /bin/sh a link to bash.exe as opposed to sh.exe before. But I remember someone saying something about ash being more stable for configures than bash. Could I run into problems because of that? - Anil Mikey wrote: > > I always wondered why configure screwed up bash > on win95, and I finally figured it out. > > Here documents in ash shell scripts > > This bug doesn't appear under NT4 SP3. [stuff deleted]
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |