On Sun, 10 Sep 2006, Paul Eggert wrote: > Tim Rice <[EMAIL PROTECTED]> writes: > > > I have no idea why SESEOF is there instead of _ASEOF > > It's probably some bug in the Unixware shell. You might be able to > use the "truss" command to verify this. If we knew more about the > bug, we might be able to work around it. > > <http://uw714doc.sco.com/en/man/html.1/sh.1.html> talks about > /u95/bin/sh, whereas your traces show that you specified > CONFIG_SHELL=/usr/bin/posix/sh. What's the difference? Does > switching to /u95/bin/sh fix your problem? How about /bin/ksh? Which > shell does 'configure' use by default, and why didn't that suffice?
Actually /usr/bin/posix/sh is the default on UnixWare as of 2.60 Prior to 2.60 it used /bin/ksh I did not specify a CONFIG_SHELL on the configure command line. /usr/bin/posix/sh is a symbolic link to /u96/bin/sh /bin/ksh is a symbolic link to /u95/bin/ksh /u95/bin/ksh and /u95/bin/sh are hard linked. Same problem with /bin/ksh -- Tim Rice Multitalents (707) 887-1469 [EMAIL PROTECTED]
