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: <37680C5A.10D3F140@acm.org>
Date: Wed, 16 Jun 1999 16:43:06 -0400
From: "D. Richard Hipp" <drh AT acm DOT org>
Organization: Hwaci
X-Mailer: Mozilla 3.0Gold (X11; U; Linux 2.0.36 i686)
MIME-Version: 1.0
To: DJ Delorie <dj AT delorie DOT com>
CC: cygwin AT sourceware DOT cygnus DOT com
Subject: Re: "sed" bug?
References: <19990616192340 DOT 14656 DOT rocketmail AT web119 DOT yahoomail DOT com> <3767FB78 DOT EE70381 AT acm DOT org> <199906162012 DOT QAA29978 AT envy DOT delorie DOT com> <37680A14 DOT 6E904CFE AT acm DOT org> <199906162037 DOT QAA30157 AT envy DOT delorie DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

DJ Delorie wrote:
> 
> More likely a bug in ash (or in cygwin, but only ash stumbles upon
> it).  We don't intentionally make them incompatible.  Note, however,
> that bash and ash *are* different programs, so if a script relies on
> some obscure bash idiosyncrasy, there's not much we can do about it.

The problems that cleared up when I switched to bash were
"sed" expressions that were generated by standard Autoconf
macros (version 1.13).  I'm guessing that Autoconf doesn't
use any obscure bash idiosyncrasies, so it looks like this
could be an ash bug.

-- 
D. Richard Hipp -- drh AT acm DOT org -- http://www.hwaci.com/drh/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com