On 11/18/2010 06:47 AM, Peter Rosin wrote:
>
> For example, the N command might cause 'sed' to exit in some cases.
> Autoconf needs to be fairly conservative about unusual 'sed' commands
> such as 'N', as 'sed' implementations are not always bug-free.
I didn't recognize that one, so I looked it up in the limitations of
sed section of the manual and it's not listed there. Perhaps it should
be? But while doing that, I did find
Unicos 9 sed loops endlessly on patterns like ‘.*\n.*’.
which I somehow missed before. Case closed, the fat lady has sung.
I don't think so. Is Unicos 9 relevant (15 year old)? Maybe this is
worth detecting anyway in AC_PROG_SED?
To fix the problem that Paul mentioned, just add a "$b" command before
the "N" commands.
Paolo
