Re: RM: to -f or not to -f

[Eric Blake]

[adding bug-libtool, replies can drop autoconf]

On 07/29/2010 10:26 AM, Patrick Welche wrote:
> I just tried configuring libxml2 which has
> 
>       AC_PATH_PROG(RM, rm, /bin/rm)
> 
> in its configure.in. After running configure
> 
>       rm: libtoolT: No such file or directory
>       Done configuring
> 
> Probably from
> 
>       cfgfile="${ofile}T"
>       trap "$RM \"$cfgfile\"; exit 1" 1 2 15
>       $RM "$cfgfile"
> 
> in config.status which in turn seems to be from _LT_CONFIG in
> libtool/libltdl/m4/libtool.m4.

Thanks for the analysis.

> 
> So, the AC_PATH_PROG(RM, rm, /bin/rm) means that libtool's RM=rm -f if
> RM wasn't defined yet doesn't happen.
> 
> Any thoughts? (just to get rid of an harmless error message)
> (BTW, autoconf, automake, libtool and libxml2 all from today's head)

I'd also seen the same line when building libvirt, but hadn't taken the
time to figure out why; libvirt indeed does:

configure.ac:AC_PATH_PROG([RM], [rm], [/bin/rm])

(but with correct m4 quoting, compared to libxml2).

There's nothing autoconf can do about it, but it might make sense for
libtool to change something.

-- 
Eric Blake   address@hidden    +1-801-349-2682
Libvirt virtualization library http://libvirt.org

signature.asc
Description: OpenPGP digital signature