In article <20020317.11022.br...@clisp.org>,
Bruno Haible wrote:
> David Evans wrote:
> > Thanks for that. I've solved the problem more simply by installed GNU
> > sed on both FreeBSD and OS X, and it now works.
>
> I confirm that with MacOS X /usr/bin/sed, MODULES.html.sh spews error
> m
David Evans wrote:
> Thanks for that. I've solved the problem more simply by installed GNU
> sed on both FreeBSD and OS X, and it now works.
I confirm that with MacOS X /usr/bin/sed, MODULES.html.sh spews error
messages from 'sed' (with or without Paul's patch), whereas with GNU sed,
MODULES.htm
In article <4eb05403.7060...@cs.ucla.edu>,
Paul Eggert wrote:
> On 11/01/11 11:12, David Evans wrote:
>
> > I will have to assume that Bash or sed on both FreeBSD and
> > OS X is broken in some way.
>
> Quite possibly, but I've run into similar issues many times over
> the years, with various
Paul Eggert wrote:
> Replace foo=` ... sed -e COMPLICATED ... ` with
> bar=COMPLICATED; foo=` ... sed -e "$bar" ... ` when COMPLICATED
> contains (possibly-quoted) backslashes.
Thanks, Paul. Nowadays I try to avoid backslashes inside backquote.
Correctly parsing backslashes inside backquote (and p
On 11/01/11 11:12, David Evans wrote:
> I will have to assume that Bash or sed on both FreeBSD and
> OS X is broken in some way.
Quite possibly, but I've run into similar issues many times over
the years, with various shells, and it's fairly easy to work around
these bugs. I installed the follow
I've now bisected this bug, and the first bad commit is fc367
Since this is many years ago, I find it hard to believe that
this file, MODULES.html.sh, had been broken for this long.
I will have to assume that Bash or sed on both FreeBSD and
OS X is broken in some way.
While running MODULES.html.sh I get this repeated error:
sed: 1: "s,\([^a-zA-Z_]\)\(FD_CL ...": unterminated substitute pattern
./gnulib-tool: line 818: printf: write error: Broken pipe
caught signal 13
Uisng the trace facility in Bash, it seems to be happening at line 1527
Tested on OS X 10.6.
