From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Alexander Shukaev Newsgroups: gmane.emacs.devel Subject: Re: Whitespace in `${srcdir}' during `configure' Date: Mon, 10 Nov 2014 17:03:12 +0100 Message-ID: References: <5460673E.8000002@cs.ucla.edu> <83389rnl75.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=089e0158bdeab3995c0507834c8d X-Trace: ger.gmane.org 1415635421 1632 80.91.229.3 (10 Nov 2014 16:03:41 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 10 Nov 2014 16:03:41 +0000 (UTC) Cc: eggert@cs.ucla.edu, emacs-devel , Yuri Khan To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 10 17:03:30 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 1XnrR8-0001yG-UB for ged-emacs-devel@m.gmane.org; Mon, 10 Nov 2014 17:03:27 +0100 Original-Received: from localhost ([::1]:43933 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XnrR8-0001zQ-Iw for ged-emacs-devel@m.gmane.org; Mon, 10 Nov 2014 11:03:26 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:59264) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XnrR4-0001z1-Hc for emacs-devel@gnu.org; Mon, 10 Nov 2014 11:03:23 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XnrQy-0004Kn-LV for emacs-devel@gnu.org; Mon, 10 Nov 2014 11:03:22 -0500 Original-Received: from mail-la0-x22c.google.com ([2a00:1450:4010:c03::22c]:47609) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XnrQv-0004JX-Ok; Mon, 10 Nov 2014 11:03:14 -0500 Original-Received: by mail-la0-f44.google.com with SMTP id gf13so7925691lab.31 for ; Mon, 10 Nov 2014 08:03:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=VJ9HkRxkWUumGJZNGXlnJydEoX/gCeporx9lLgC+ndE=; b=lE0kj5NQ9GvKdtucPHUUUuBRQwNr2212R9St7lkGlx2GJbgfN4Fba2ZeAPge8MqI7R aIUJUPvTBP4qj9JzYC0jb9iS3quyp2ljjpZAsEST9DmWlPsDrdPiw6GzLczNH/3B9j0J 99JnUPdKYuOU7OMS06EsWjdoyh4xX9s2JkUzsyjd8LJHRdeCN52dHm4+k+tPzoBzmEJR tmdXuc2XDZU6/B83dtbmftC0cCj6f61i17P1DP8jXrITiG0Uja1Tcj7GeUcjQEIDt384 zYknL05qYI84TM4k9r/GB3v9E1vjFHk20XVCh2090ytuuWca1KbeeHKuu1YKOqW7xrur x4wg== X-Received: by 10.152.27.38 with SMTP id q6mr3155387lag.92.1415635392499; Mon, 10 Nov 2014 08:03:12 -0800 (PST) Original-Received: by 10.112.202.106 with HTTP; Mon, 10 Nov 2014 08:03:12 -0800 (PST) In-Reply-To: <83389rnl75.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4010:c03::22c 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:176687 Archived-At: --089e0158bdeab3995c0507834c8d Content-Type: text/plain; charset=UTF-8 > > 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. Yes, this case occurs not too often, but directories with spaces are generally allowed and therefore should be supported. It's an element of build robustness after all. 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. --089e0158bdeab3995c0507834c8d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thi= s all is true, but it is not really relevant, since these
<= /div> 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. Yes= terday I've tried to build it in a directory "C:\Users\Haroogan\Pr= ojects\Bitbucket\Emacs for Windows", where name corresponds to the nam= e of the project on Bitbucket. Yes, this case occurs not too often, but dir= ectories with spaces are generally allowed and therefore should be supporte= d. It's an element of build robustness after all.

My patch at least prevents:=

configure: line= 3557: ...: No such file or directory

And leads to the official error:

checking whether bu= ild environment is sane... configure: error: unsafe srcdir value: ...

and = this limitation might be gone someday. So it is still worth applying I beli= eve.
--089e0158bdeab3995c0507834c8d--