[sudo-workers] sudo 1.6.8p1 configure problems on SunOS4 ...

[Todd C. Miller]

Aha.  configure found bash in my path and re-execed itself using
that instead of /bin/sh.  Now I see the behavior you describe.

Apparently there was a bug in sh in SunOS 4.1.3 where it used the
wrong pid for its temp files.

See this thread:
http://lists.gnu.org/archive/html/autoconf/2002-08/msg00019.html

However, even with the latest sh patch from Sun I still get the
bogus behavior.  It is clear to me that this is a bug in SunOS's
sh and not sudo (check /tmp for lots of orphaned shell temp files).
I suspect the large amount of here documents and evals in configure
has something to do with triggering it.  At one point there were
over 1357 sh temp files in my /tmp for a single configure run (most
of them were cleaned up though)

If you have bash, ksh or zsh installed, try running configure through
one of those.  Also, the stock sed chews up a lot of cpu time as
well.

 - todd