Re: non portable sed scripts

[Tim Rice]

On Mon, 22 May 2006, Ralf Wildenhues wrote:

> Well, my guess is still that (at least one sed on) UnixWare has similar
> issues, but I have no idea whether this UnixWare has several sed
> implementations, and one of them is usable, or whether it is common to
> have GNU sed as add-on installed and in $PATH.

UnixWare only has one sed. But there so many open source projects out
there that use GNU specific features os sed that it is common for
people doing development on UnixWare to install a GNU sed.

> Tim, could you do us a favor and test this patch?  It should apply to
> Autoconf-2.59c or CVS Autoconf, and the interesting test output would
> be in tests/testsuite.log after
> 
>   env TESTSUITEFLAGS='-k config.status -k AC_PROG_SED' make -e check

Looks good on my UnxiWare 7.1.4 box.
...
/usr/bin/posix/sh ./testsuite -k config.status -k AC_PROG_SED
## ------------------------------ ##
## GNU Autoconf 2.59c test suite. ##
## ------------------------------ ##

Testing config.status.

 81: Torturing config.status                       ok

Testing autoconf/programs macros.

203: AC_PROG_SED                                   ok

## ------------- ##
## Test results. ##
## ------------- ##

All 2 tests were successful.
...

Not so good on my OpenServer 5.0.4 box
...
gmake[2]: Entering directory `/usr/local/src/gnu/autoconf-2.59c/tests'
/bin/ksh ./testsuite -k config.status -k AC_PROG_SED
/testsuite[900]: : is not an identifier
gmake[2]: *** [check-local] Error 1
...

BTW, This hunk failed on autoconf-2.59c as it was already 3.
> -ac_max_sed_lines=m4_eval(_AC_SED_CMD_LIMIT - 4)
> +ac_max_sed_lines=m4_eval(_AC_SED_CMD_LIMIT - 3)


-- 
Tim Rice                                Multitalents    (707) 887-1469
address@hidden