Re: libtool breaks if arg is explicit null string

[Robert Boehne]

John Reiser wrote:
> 
> Robert Boehne wrote:
> >
> > John Reiser wrote:
> > >
> > > ltmain.sh (GNU libtool) 1.4 (1.920 2001/04/24 23:26:18)
> > >
> > > In --mode=execute, an explicit null string  ''  is not handled correctly
>   [snipped]
> 
> > Why are you trying to execute '' ?
> 
> The command line is
>         libtool --mode=execute myprog arg1 '' arg3
> 
> where the second argument to myprog is an explicit null string.
> But libtool hangs ['sed' reading stdin] during the check for whether
> the null string argument is the name of a library that libtool
> must change to reflect uninstalled status or not.  The null
> argument is the business of myprog.
> 
> In general, any "$file" containing shell metacharacters will cause
> trouble because
>         sed -e 4q  $file  |  ...
> forgot to quote   "$file" .
> 

OK, I see.  Do any of the maintainers have a problem with such
a change?  It looks harmless, but the quoting in libtool is
VERY sensitive to changes, and I'd guess that the "" were left
out originally for a reason.
If you'd like proof that quoting is sensitive, grep the
ChangeLogs for 'quot'.  :)
We do have plans to eliminate all of these problems, but it
will be some time before a binary libtool is available.

Robert

-- 
Robert Boehne             Software Engineer
Ricardo Software   Chicago Technical Center
TEL: (630)789-0003 x. 238
FAX: (630)789-0127
email:  address@hidden