From: "D. Richard Hipp" <drh@acm.org>
To: DJ Delorie <dj@delorie.com>
Cc: cygwin@sourceware.cygnus.com
Subject: Re: "sed" bug?
Date: Wed, 30 Jun 1999 22:10:00 -0000 [thread overview]
Message-ID: <37680C5A.10D3F140@acm.org> (raw)
Message-ID: <19990630221000.2VX4i4sp4c4kfIgmzRTxJcG0nJLYDi4bRMgHakPi0dw@z> (raw)
In-Reply-To: <199906162037.QAA30157@envy.delorie.com>
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@acm.org -- http://www.hwaci.com/drh/
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~1999-06-30 22:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-16 12:23 Earnie Boyd
1999-06-16 12:31 ` D. Richard Hipp
1999-06-16 13:13 ` DJ Delorie
1999-06-16 13:33 ` D. Richard Hipp
1999-06-16 13:37 ` DJ Delorie
1999-06-16 13:43 ` D. Richard Hipp [this message]
1999-06-30 22:10 ` D. Richard Hipp
1999-06-30 22:10 ` DJ Delorie
1999-06-30 22:10 ` D. Richard Hipp
1999-06-30 22:10 ` DJ Delorie
1999-06-30 22:10 ` D. Richard Hipp
1999-06-30 22:10 ` Earnie Boyd
-- strict thread matches above, loose matches on Subject: below --
1999-06-17 5:58 Eddelbuettel, Dirk
1999-06-30 22:10 ` Eddelbuettel, Dirk
1999-06-17 5:36 Earnie Boyd
1999-06-17 9:47 ` itz
1999-06-17 22:35 ` Glenn Spell
1999-06-30 22:10 ` Glenn Spell
1999-06-30 22:10 ` itz
1999-06-30 22:10 ` Earnie Boyd
1999-06-16 12:02 D. Richard Hipp
1999-06-30 22:10 ` D. Richard Hipp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=37680C5A.10D3F140@acm.org \
--to=drh@acm.org \
--cc=cygwin@sourceware.cygnus.com \
--cc=dj@delorie.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).