Re: Whitespace in `${srcdir}' during `configure'

[Eli Zaretskii <eliz@gnu.org>]

> Date: Mon, 10 Nov 2014 17:03:12 +0100
> From: Alexander Shukaev <haroogan@gmail.com>
> Cc: Yuri Khan <yuri.v.khan@gmail.com>, Glenn Morris <rgm@gnu.org>, eggert@cs.ucla.edu, 
> 	emacs-devel <emacs-devel@gnu.org>
> 
>     This all is true, but it is not really relevant, since these
>     directories are rarely if ever seen in Emacs build process on Windows
>     (because we use MSYS for that, which has different ideas about these
>     directories.
> 
> It is relevant. Yesterday I've tried to build it in a directory
> "C:\Users\Haroogan\Projects\Bitbucket\Emacs for Windows", where name
> corresponds to the name of the project on Bitbucket.

All I said is that the claim that almost every Windows user will have
these problems because Windows puts HOME in a directory with
whitespace is not relevant to the issue at hand.

I didn't say that directories with whitespace cannot happen.  I just
said that if they happen, they do because the _user_ have chosen to
build in such a directory, not because Windows did that behind the
user's back.  IOW, there's no difference between Windows and Unix in
this regard.

> My patch at least prevents:
> 
>     configure: line 3557: ...: No such file or directory
> 
> And leads to the official error:
> 
>     checking whether build environment is sane... configure: error: unsafe
>     srcdir value: ...
> 
> and this limitation might be gone someday. So it is still worth applying I
> believe.

I don't think your patch was rejected.  I think Paul encouraged you to
submit a more radical patch, so as to solve this problem in a more
complete way.