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

[Ralf Wildenhues]

* Nicolas Joly wrote on Tue, Jun 07, 2005 at 12:10:47PM CEST:
> On Sun, Jun 05, 2005 at 07:38:59PM +0200, Ralf Wildenhues wrote:
> > 
> >   CONFIG_SHELL=/bin/foosh /bin/foosh path/to/configure [OPTIONS..]
> > 
> > and you should provide an echo which does not interpret backslashes
> > (one of `echo', `/bin/echo', `print -r', `printf %s\\n' should usually
> > do).
> 
> 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 :

Please rerun the libtool command line with --debug and post output,
you may pack (gzip, bzip2).

Regards,
Ralf

> [...]
> libtool: compile:  cc "-DHAVE_CONFIG_H=<config.h>" -DLTDL -I. -I. -I.. -I. 
> -I. -I./libltdl -g -c -MD loaders/dlopen.c -o dlopen.o >/dev/null 2>&1
> /bin/ksh ../libtool --tag=CC   --mode=link cc  -g -module -avoid-version  -o 
> dlopen.la  dlopen.lo  
> ../libtool[24]: invalid multibyte character
> ../libtool[6]: invalid multibyte character
> ../libtool[2312]: invalid multibyte character
> libtool: link: invalid operation mode `link'
> libtool: link: Try `libtool --help --mode=link' for more information.
> ../libtool[7679]: invalid multibyte character
> ../libtool[7679]: invalid multibyte character
> ../libtool[7679]: invalid multibyte character
> [...]
> ../libtool[7679]: invalid multibyte character
> ../libtool[7679]: invalid multibyte character
> gmake[3]: *** [dlopen.la] Segmentation fault
> gmake[3]: Leaving directory `/home/njoly/temp/libtool/libltdl'
> gmake[2]: *** [all] Error 2