Re: FYI: ksh bug on Tru64 UNIX causes current libtool failure

[Ralf Wildenhues]

Hi Nicolas, others,

This is a gentle reminder that this issue with Libtool HEAD/branch-2-0
on Tru64 sh is still unsolved.  It'd be nice to get a solution into the
next 2.0 release candidate, should such a solution exist.

* Nicolas Joly wrote on Tue, Jun 07, 2005 at 07:59:58PM CEST:
> On Tue, Jun 07, 2005 at 03:31:22PM +0200, Ralf Wildenhues wrote:
> > * Nicolas Joly wrote on Tue, Jun 07, 2005 at 01:27:25PM CEST:
> > > On Tue, Jun 07, 2005 at 12:35:00PM +0200, Ralf Wildenhues wrote:
> > > > * Nicolas Joly wrote on Tue, Jun 07, 2005 at 12:10:47PM CEST:
> > > > > 
> > > > > In the mean time, i tested the solution where `print -r' and `ksh'
> > > > > tests are swapped (attached patch). It seems to go a little further
> > > > > (no more `print' error messages), but seems to fail in another ksh
> > > > > problem/bug :
> > 
> > [ which ends in a segmentation fault. ]

> > OK, let's cut this testing a little short.  It seems that Tru64 fails to
> > provide any decent kind of shell for its users.
> > 
> > I consider just putting a note about Tru64 into README (branch-1-5)
> > resp. doc/notes.texi (HEAD).   Proposal would be one of the following
> > (whichever works and passes the test suite):
> > 
> > | Note that Tru64 V5.1B ksh has some bugs which make it hardly useable for
> > | libtoolized packages.  Please set
> > |   BIN_SH=xpg4; export BIN_SH
> > | in your environment for configuring and building.
> 
> This one does not work ... It will solve the `print' problem, but will
> lead to the shell crash a little later.
> 
> with `BIN_SH=xpg4' set, `/usr/bin/posix/sh' is executed instead of the
> classic `/bin/sh'; and, unfortunately, this is a hard link to `ksh'.
> 
> address@hidden [~]> ls -ldi /usr/bin/posix/sh /usr/bin/ksh 
>   482 -rwxr-xr-x   2 bin      bin       307248 Oct 16  2002 /usr/bin/ksh
>   482 -rwxr-xr-x   2 bin      bin       307248 Oct 16  2002 /usr/bin/posix/sh
> 
> > | Note that Tru64 V5.1B ksh has some bugs which make it hardly useable for
> > | libtoolized packages.  Please set
> > |   lt_ECHO='printf %s\\n'; export lt_ECHO
> > | in your environment for configuring and building.
> > 
> > (s/lt_ECHO/ECHO/g for branch-1-5).

Regards,
Ralf