Hello Arkadiusz, * Arkadiusz Miskiewicz wrote on Tue, Jul 28, 2009 at 12:47:23PM CEST: > autoconf 2.64 fails when IFS is changed while 2.63 works fine > > [ar...@carme-pld ~/test/1]$ cat configure.ac
> AC_PREREQ([2.64]) > AC_INIT([FULL-PACKAGE-NAME], [VERSION], [BUG-REPORT-ADDRESS]) > > old_IFS=$IFS > IFS="," > AC_DEFINE([VC_ENABLE_API_COMPAT], [1]) > IFS="$old_IFS" > > AC_OUTPUT > > [ar...@carme-pld ~/test/1]$ aclocal; autoconf > > [ar...@carme-pld ~/test/1]$ ./configure > ./configure[1640]: print -r --: not found > configure: creating ./config.status > > [ar...@carme-pld ~/test/1]$ autoconf --version > autoconf (GNU Autoconf) 2.64 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. Cheers, Ralf
