From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Whitespace in `${srcdir}' during `configure' Date: Mon, 10 Nov 2014 18:27:12 +0200 Message-ID: <83zjbzm36n.fsf@gnu.org> References: <5460673E.8000002@cs.ucla.edu> <83389rnl75.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1415636863 28816 80.91.229.3 (10 Nov 2014 16:27:43 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 10 Nov 2014 16:27:43 +0000 (UTC) Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org, yuri.v.khan@gmail.com To: Alexander Shukaev Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 10 17:27:37 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1XnroW-0005Uu-TV for ged-emacs-devel@m.gmane.org; Mon, 10 Nov 2014 17:27:37 +0100 Original-Received: from localhost ([::1]:44020 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XnroW-0002Al-Gr for ged-emacs-devel@m.gmane.org; Mon, 10 Nov 2014 11:27:36 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:37240) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XnroP-0002AQ-3y for emacs-devel@gnu.org; Mon, 10 Nov 2014 11:27:34 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XnroJ-0005Iw-U5 for emacs-devel@gnu.org; Mon, 10 Nov 2014 11:27:29 -0500 Original-Received: from mtaout28.012.net.il ([80.179.55.184]:60904) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XnroJ-0005I4-LQ; Mon, 10 Nov 2014 11:27:23 -0500 Original-Received: from conversion-daemon.mtaout28.012.net.il by mtaout28.012.net.il (HyperSendmail v2007.08) id <0NET00H00ZWIDU00@mtaout28.012.net.il>; Mon, 10 Nov 2014 18:24:38 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout28.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NEU00H7L092TH10@mtaout28.012.net.il>; Mon, 10 Nov 2014 18:24:38 +0200 (IST) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 80.179.55.184 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:176690 Archived-At: > Date: Mon, 10 Nov 2014 17:03:12 +0100 > From: Alexander Shukaev > Cc: Yuri Khan , Glenn Morris , eggert@cs.ucla.edu, > emacs-devel > > 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.