From: Eli Zaretskii <eliz@gnu.org>
To: Alexander Shukaev <haroogan@gmail.com>
Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org, yuri.v.khan@gmail.com
Subject: Re: Whitespace in `${srcdir}' during `configure'
Date: Mon, 10 Nov 2014 18:27:12 +0200 [thread overview]
Message-ID: <83zjbzm36n.fsf@gnu.org> (raw)
In-Reply-To: <CAKu-7WzneMnjbHC5Q0ncN5_uk485aB5pN-+y=UP7ScmHPRFS=w@mail.gmail.com>
> 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.
next prev parent reply other threads:[~2014-11-10 16:27 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
2014-11-10 16:27 ` Eli Zaretskii [this message]
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=83zjbzm36n.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=haroogan@gmail.com \
--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).