On Fri, 2015-01-02 at 16:06 -0700, Eric Blake wrote: > While paths with spaces in them may be a fact of reality, they are > non-portable according to POSIX. It is going to be an uphill battle if > you want to submit patches to make autoconf automatically handle file > names with spaces, as there is nothing portable about them. We all agree they're not portable. We also all agree autoconf is intended to generate portable configure scripts. If this were ever patched, it would probably involve some clever way of distinguishing spaces in paths from argument separators in the argument vector. The only way I can see this ever happening is if argument vectors were prepared through higher level functions, such as M4 macros, with different functions to distinguish the two semantics. -- Kip Warner -- Senior Software Engineer OpenPGP encrypted/signed mail preferred http://www.thevertigo.com
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Autoconf mailing list Autoconf@xxxxxxx https://lists.gnu.org/mailman/listinfo/autoconf
