Re: autoconf 2.64 fails when IFS is changed

[Eric Blake]

According to Ralf Wildenhues on 7/28/2009 12:39 PM:
> Hello Arkadiusz,
> 
>> old_IFS=$IFS
>> IFS=","
>> AC_DEFINE([VC_ENABLE_API_COMPAT],   [1])
>> IFS="$old_IFS"
>>
>> AC_OUTPUT
>> address@hidden ~/test/1]$ ./configure
>> ./configure[1640]: print -r --: not found
>> configure: creating ./config.status
>>
> Thanks for the report.  This will probably mean that we will document
> that you should not change, or that you need to restore, IFS when
> invoking Autoconf macros.  In general, we really cannot guarantee which
> macros will expand to IFS-sensitive code and which won't, so you may
> have to assume they all will.

Cleaning out some old mails in my inbox.  I agree with Ralf that the best
we can do is document IFS better (it is easier to do that than to ask all
internal uses of $* to reset IFS to the defaults).  I will be pushing this.

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

autoconf.patch252
Description: Text document

signature.asc
Description: OpenPGP digital signature