Re: autoconf-2.65 on UnixWare 7.1.4

[Tim Rice]

On Tue, 12 Jan 2010, Tim Rice wrote:

> Hi Ralf,
> 
> On Tue, 12 Jan 2010, Ralf Wildenhues wrote:
> 
> > * Tim Rice wrote on Tue, Jan 12, 2010 at 01:48:43AM CET:
> > > On Mon, 11 Jan 2010, Ralf Wildenhues wrote:
> > > [snip]
> > > > > > 1. micro-suite.at:2: 1. pass: no trailing newline 
> > > > > > (micro-suite.at:2): FAILED (micro-suite.at:3)
> > > > > 127. autotest.at:397: 127. Binary output (autotest.at:397): FAILED 
> > > > > (autotest.at:397)
> > > > 
> > > > Apparently your shell has a bug with output not ending in a newline: it
> > > > appears that some string has not been suitably \0-terminated or so.
> > > > 
> > > > I'm not sure whether it is useful to let configure avoid such a shell,
> > > > but you might want to try
> > > >   make check TESTSUITEFLAGS='-v -d -x 127 CONFIG_SHELL=/bin/bash'
> > > > instead of using /bin/ksh, to see whether that makes the test pass.
> > > 
> > > Unfortunatly these systems do not ship with a bash.
> > 
> > Do they ship with any shell that passes this test and is otherwise
> > reasonable?
> 
> Unfortunatly we're already selecting the best (least tests fail) shell
> that ships with the system.
> /bin/sh will pass test 127 (and 226) but fails 123 133 134 and 211.

Now I'm not so sure.
 
> I started working on building bash-4.1 last night.
> When I get that built, I'll see if it works any better.

I re-ran test 127 with
   gmake check TESTSUITEFLAGS='-v -d -x 127 CONFIG_SHELL=/bin/sh'
and
   gmake check TESTSUITEFLAGS='-v -d -x 127 CONFIG_SHELL=/opt/bin/bash'

See attached sh-testsuite.log.gz and bash-4.1-testsuite.log.gz
In both cases the inner tests fail but the last line says test 127 is ok.
Strange.
At least ksh says 127 failed.

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

sh-testsuite.log.gz
Description: Binary data

bash-4.1-testsuite.log.gz
Description: Binary data