I got much farther with /bin/sh5:
...
configure: creating ./config.status
sed: Unexpected End-of-file
/bin/sh5: ^Jsrcdir=..^JINSTALL=/usr/bin/install: not found
configure: WARNING: you should use --build, --host, --target
configure: WARNING: invalid host type: --enable-parse-clocks
configure: error: unrecognized option: --no-recursion
exec /bin/sh5 ../configure --enable-parse-clocks --no-create
--no-recursion ;;
--version | --vers* | -V )
echo ; exit 0 ;;
--he | --h)
# Conflict between --help and --header
{ { echo config.status:14561:
Try `../configure --help' for more information.
/bin/sh5: Try: not found
Harlan
> > From: Jim Meyering <[EMAIL PROTECTED]>
> > Date: 19 Mar 2001 10:52:15 +0100
> >
> > I'm beginning to think that Ultrix's /bin/sh is so bad that polluting,
> > er... changing autoconf to accommodate is may not be worthwhile.
> > Do any of you have an idea of how big the Ultrix-using community is?
>
> I don't really know, but I'd guess less than a thousand sysadmins
> total, and of those maybe a few dozen sysadmins use autoconf-derived
> scripts.
>
> Sorry, I lost context. Why can't we ask people to invoke
> 'CONFIG_SHELL=/bin/sh5 /bin/sh5 configure' on Ultrix? If there's only
> a few dozen users, we can just inform them of this by hand.