unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alexander Shukaev <haroogan@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: eggert@cs.ucla.edu, emacs-devel <emacs-devel@gnu.org>,
	Yuri Khan <yuri.v.khan@gmail.com>
Subject: Re: Whitespace in `${srcdir}' during `configure'
Date: Mon, 10 Nov 2014 17:03:12 +0100	[thread overview]
Message-ID: <CAKu-7WzneMnjbHC5Q0ncN5_uk485aB5pN-+y=UP7ScmHPRFS=w@mail.gmail.com> (raw)
In-Reply-To: <83389rnl75.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 877 bytes --]

>
> 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.

[-- Attachment #2: Type: text/html, Size: 1877 bytes --]

  reply	other threads:[~2014-11-10 16:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-10  2:28 Whitespace in `${srcdir}' during `configure' Alexander Shukaev
2014-11-10  7:14 ` Glenn Morris
2014-11-10  7:20   ` Paul Eggert
2014-11-10  8:26     ` Glenn Morris
2014-11-10 14:28       ` Yuri Khan
2014-11-10 15:12         ` Eli Zaretskii
2014-11-10 16:03           ` Alexander Shukaev [this message]
2014-11-10 16:27             ` Eli Zaretskii
2014-11-10 17:17             ` Glenn Morris
2014-11-10 18:04               ` Alexander Shukaev
2014-11-10 19:25                 ` Glenn Morris
2014-11-10 19:39                   ` Glenn Morris
2014-11-17  2:24                     ` Glenn Morris
2014-11-10 10:47     ` Eli Zaretskii
2014-11-10  7:17 ` Paul Eggert
2014-11-10  7:24   ` Glenn Morris
2014-11-10  9:04     ` Andreas Schwab

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAKu-7WzneMnjbHC5Q0ncN5_uk485aB5pN-+y=UP7ScmHPRFS=w@mail.gmail.com' \
    --to=haroogan@gmail.com \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=yuri.v.khan@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).