Re: non portable sed scripts

[Tim Rice]

On Tue, 23 May 2006, Ralf Wildenhues wrote:

> > > Pleas try again with /usr/bin/posix/sh as shell; that's what the shell
> > > selection algorithm of 2.59c will select.
> > 
> > Yes that fails. /usr/bin/posix/sh is a symbolic link to /u95/bin/sh which
> > is hard linked to /u95/bin/ksh. /usr/bin/ksh is a symbolic link to
> > /u95/bin/ksh.
> > 
[snip]
> So I assume we have an incarnation of a bug similar to this one
> (quoting `info Autoconf "Here-Documents"'):
> 
> |    Many older shells (including the Bourne shell) implement
> | here-documents inefficiently.  And some shells mishandle large
> | here-documents: for example, Solaris `dtksh', which is derived from
> | Korn shell version M-12/28/93d, mishandles variable expansion that
> | occurs on 1024-byte buffer boundaries within a here-document.  Users
> | can generally fix these problems by using a faster or more reliable
> | shell, e.g., by using the command `CONFIG_SHELL=/bin/bash /bin/bash
> | ./configure' rather than plain `./configure'.

I'd say the identical bug.
...
$ what /usr/bin/ksh | grep -i version
        Version M-12/28/93e-SCO
...

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