Re: ksh bug on Tru64 UNIX causes current libtool failure

[Ralf Wildenhues]

Hi Nicolas,

* Nicolas Joly wrote on Wed, May 18, 2005 at 05:03:05PM CEST:
> 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:
*snip*
> /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

That'll teach me to ever do fatal errors based on shell correctness
assumptions again.  :(

Could you as well please: run the script I sent in another message in
this thread and report the exact ksh version this is on, so we can
mention it in the Autoconf portability section?

Just to see whether I have missed any other occurrences: Does libtool
compile and work with the patch below (except maybe a lot of extraneous
quotes)?

And for possible workarounds:  Does Tru64 ship another shell suitable
for use as CONFIG_SHELL?  Please try with
  CONFIG_SHELL=/bin/foosh /bin/foosh path/to/libtool/configure [OPTIONS]

I believe it might be the best to just completely back out the other
patch again (as well as the one below).  :(

Regards,
Ralf

diff -u -r1.334.2.69 ltmain.in
--- ltmain.in   4 May 2005 13:52:10 -0000       1.334.2.69
+++ ltmain.in   18 May 2005 21:07:44 -0000
@@ -742,7 +742,6 @@
     esac
     if test "X$libobj" != "X$qlibobj"; then
        $echo "$modename: libobj name \`$libobj' may not contain shell special 
characters."
-       exit $EXIT_FAILURE
     fi
     objname=`$echo "X$obj" | $Xsed -e 's%^.*/%%'`
     xdir=`$echo "X$obj" | $Xsed -e 's%/[^/]*$%%'`