Re: ksh bug on Tru64 UNIX causes current libtool failure

[Albert Chin]

On Wed, May 18, 2005 at 05:03:05PM +0200, Nicolas Joly wrote:
> On Wed, May 18, 2005 at 08:33:01AM +0200, Ralf Wildenhues wrote:
> > 
> > If not, let me see: This failure only causes quote.test to fail, and
> > causes a lot of extra quotes in the libtool output, but no real failure.
> > Is that correct?
> 
> Not really.
> 
> I can't even compile libtool 1.5.18 on my Tru64 unix V5.1B
> workstation:
> 
> address@hidden [~]> sizer -v
> Compaq Tru64 UNIX V5.1B (Rev. 2650); Fri Jun 18 18:36:47 CEST 2004
> address@hidden [src/libtool-1.5.18]> make
> No suffix list.
> Making all in .
> No suffix list.
> CONFIG_FILES=libtoolize CONFIG_HEADERS= /bin/ksh ./config.status
> config.status: creating libtoolize
> config.status: executing depfiles commands
> chmod +x libtoolize
> Making all in libltdl
> make  all-am
> /bin/ksh ./libtool --tag=CC --mode=compile cc -DHAVE_CONFIG_H  -I. -I. -I.    
>   -g -c -o ltdl.lo ltdl.c
> libtool: compile: libobj name `ltdl.lo' may not contain shell special 
> characters.
> *** Exit 1

This is a result of the ksh bug.

-- 
albert chin (address@hidden)