From: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
To: Dave Korn <dave.korn.cygwin@googlemail.com>
Cc: Paolo Bonzini <bonzini@gnu.org>,
NightStrike <nightstrike@gmail.com>,
gcc@gcc.gnu.org, davek@gcc.gnu.org, Mook - <mook.gcc@gmail.com>,
Kai Tietz <ktietz70@googlemail.com>
Subject: Re: r150960 changed ltmain.sh and broke the build
Date: Wed, 26 Aug 2009 18:51:00 -0000 [thread overview]
Message-ID: <20090826174825.GD9074@gmx.de> (raw)
In-Reply-To: <4A9510BA.1030704@gmail.com>
* Dave Korn wrote on Wed, Aug 26, 2009 at 12:38:50PM CEST:
> Paolo Bonzini wrote:
> > $ sed -e 's,/\(\./\)\{1\,\},/,g;s,/\.$,/,'
> > ./foo/bar/./baz
> > ./foo/bar/baz
> >
> > $ sed -e 's,/\(\./\)\{1,\},/,g;s,/\.$,/,'
> > sed: -e expression #1, char 18: unknown option to `s'
> >
> > $
>
> Maybe the best thing would be to change it to use a different separator?
> Ralf, have we discovered a new item for the autoconf man page "portable shell"
> chapter?
Not really:
Patterns should not include the separator (unless escaped), even
as part of a character class. In conformance with Posix, the Cray
`sed' rejects `s/[^/]*$//': use `s,[^/]*$,,'.
[...]
Portable `sed' regular expressions should use `\' only to escape
characters in the string `$()*.0123456789[\^n{}'.
Sorry for not catching this.
Cheers,
Ralf
next prev parent reply other threads:[~2009-08-26 17:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 10:27 NightStrike
2009-08-26 10:34 ` Dave Korn
2009-08-26 10:47 ` Paolo Bonzini
2009-08-26 10:50 ` Paolo Bonzini
2009-08-26 10:51 ` Dave Korn
2009-08-26 11:04 ` Paolo Bonzini
2009-08-26 13:00 ` Dave Korn
2009-08-26 13:31 ` Paolo Bonzini
2009-08-26 13:32 ` Dave Korn
2009-08-27 16:51 ` Eric Blake
2009-08-27 22:51 ` Dave Korn
2009-08-26 18:51 ` Ralf Wildenhues [this message]
2009-08-26 19:03 ` Dave Korn
2009-08-26 19:23 ` Ralf Wildenhues
2009-08-26 20:32 ` Paolo Bonzini
2009-08-26 21:30 ` Dave Korn
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=20090826174825.GD9074@gmx.de \
--to=ralf.wildenhues@gmx.de \
--cc=bonzini@gnu.org \
--cc=dave.korn.cygwin@googlemail.com \
--cc=davek@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=ktietz70@googlemail.com \
--cc=mook.gcc@gmail.com \
--cc=nightstrike@gmail.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).