[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: FYI: ksh bug on Tru64 UNIX causes current libtool failure
From: |
Nicolas Joly |
Subject: |
Re: FYI: ksh bug on Tru64 UNIX causes current libtool failure |
Date: |
Tue, 7 Jun 2005 19:59:58 +0200 |
User-agent: |
Mutt/1.5.8i |
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. ]
>
> > > Please rerun the libtool command line with --debug and post output,
> > > you may pack (gzip, bzip2).
> >
> > libtool.dbg.bz2 attached.
>
> 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).
Will test, and report.
> What do you think? Which one? Could one of the Tru64 users be bothered
> to send a bug report to HP?
Sorry i can't.
Our sysadmins tried to have a software support contract from
Digital/Compaq for many years, but didn't get any succes ! They give
up when HP came up ...
--
Nicolas Joly
Biological Software and Databanks.
Institut Pasteur, Paris.
Re: ksh bug on Tru64 UNIX causes current libtool failure, Nicolas Joly, 2005/06/02
- FYI: ksh bug on Tru64 UNIX causes current libtool failure, Ralf Wildenhues, 2005/06/05
- Re: FYI: ksh bug on Tru64 UNIX causes current libtool failure, Nicolas Joly, 2005/06/07
- Re: FYI: ksh bug on Tru64 UNIX causes current libtool failure, Ralf Wildenhues, 2005/06/07
- Re: FYI: ksh bug on Tru64 UNIX causes current libtool failure, Nicolas Joly, 2005/06/07
- Re: FYI: ksh bug on Tru64 UNIX causes current libtool failure, Ralf Wildenhues, 2005/06/07
- Re: FYI: ksh bug on Tru64 UNIX causes current libtool failure,
Nicolas Joly <=
Re: ksh bug on Tru64 UNIX causes current libtool failure, Ralf Wildenhues, 2005/06/07