From: Dani Moncayo <dmoncayo@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Alexander Shukaev <haroogan@gmail.com>, 18955@debbugs.gnu.org
Subject: bug#18955: Makefile:382: recipe for target 'src' failed
Date: Sun, 9 Nov 2014 21:10:58 +0100 [thread overview]
Message-ID: <CAH8Pv0hKGMK6tb-Qm-1=2kW4Mz_JRZifrs+Od42T8xQhQdVdDA@mail.gmail.com> (raw)
In-Reply-To: <83vbmonoky.fsf@gnu.org>
> It's not Emacs who becomes confused, it's MSYS. When MSYS invokes a
> native Windows program, it converts /c/foo/bar file names into the
> Windows C:\foo\bar form, because otherwise native Windows programs
> will not be able to access such files. There's some logic in MSYS
> that is used to decide when to do this conversion, and that logic
> fails when the /c/foo/bar file name is not at the beginning of the
> command-line argument, as in this case.
Indeed, and FWIW, that logic is documented here:
http://www.mingw.org/wiki/Posix_path_conversion
> That's why we use
> unmsys--file-name: to paper over these failures of MSYS.
>
>> I believe it's better to teach it to treat "/C" as "C:" by default, i.e. to
>> accept both variants because there is no ambiguity here and, as a result, it
>> will support both Windows and MSYS(2)/Cygwin paths out of the box.
MSYS paths are not only those of the form "/c/foo". For example:
"/home/dani/foo", "/usr/local" and, in general any UNIX-like path are
valid MSYS paths.
And moreover, any MSYS path could be mounted to any Windows-native
path (type "mount" to see the current mapping).
Therefore, it is clear that supporting MSYS/Cygwin paths from the
MS-Windows port of Emacs is far more complex that simply translating
"/C" into "C:".
--
Dani Moncayo
next prev parent reply other threads:[~2014-11-09 20:10 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 15:52 bug#18955: Makefile:382: recipe for target 'src' failed Alexander Shukaev
2014-11-05 16:55 ` Glenn Morris
2014-11-05 17:03 ` Alexander Shukaev
2014-11-05 17:04 ` Glenn Morris
[not found] ` <CAKu-7WzwmwmqCswS+b32zdY6DLZb7G=uLu-8FZjCQgVUvBwNRQ@mail.gmail.com>
2014-11-05 17:33 ` bug#18955: Fwd: " Alexander Shukaev
2014-11-05 17:39 ` Alexander Shukaev
2014-11-05 18:31 ` Glenn Morris
2014-11-05 22:41 ` Alexander Shukaev
2014-11-06 3:48 ` Eli Zaretskii
2014-11-06 13:17 ` Alexander Shukaev
2014-11-06 16:30 ` Eli Zaretskii
2014-11-06 18:48 ` Alexander Shukaev
2014-11-06 19:21 ` Eli Zaretskii
2014-11-06 20:56 ` Alexander Shukaev
2014-11-07 15:02 ` Alexander Shukaev
2014-11-07 15:21 ` Eli Zaretskii
2014-11-07 15:34 ` Alexander Shukaev
2014-11-07 15:36 ` Alexander Shukaev
2014-11-07 15:50 ` Eli Zaretskii
2014-11-07 15:56 ` Alexander Shukaev
2014-11-07 15:57 ` Alexander Shukaev
2014-11-07 19:53 ` Eli Zaretskii
2014-11-07 19:52 ` Eli Zaretskii
2014-11-09 17:30 ` Eli Zaretskii
2014-11-09 17:42 ` Alexander Shukaev
2014-11-09 19:47 ` Eli Zaretskii
2014-11-09 20:10 ` Dani Moncayo [this message]
2014-11-09 20:15 ` Eli Zaretskii
2014-11-09 20:25 ` Alexander Shukaev
2014-11-09 20:33 ` Eli Zaretskii
2014-11-09 20:43 ` Dani Moncayo
2014-11-09 20:46 ` Eli Zaretskii
2014-11-09 20:13 ` Alexander Shukaev
2014-11-09 20:28 ` Eli Zaretskii
2014-11-09 20:38 ` Alexander Shukaev
2014-11-09 20:43 ` Alexander Shukaev
2014-11-09 20:49 ` Eli Zaretskii
2014-11-09 22:43 ` Glenn Morris
2014-11-10 7:17 ` Glenn Morris
2014-11-09 20:47 ` Eli Zaretskii
2014-11-05 19:00 ` bug#18955: Fwd: " Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH8Pv0hKGMK6tb-Qm-1=2kW4Mz_JRZifrs+Od42T8xQhQdVdDA@mail.gmail.com' \
--to=dmoncayo@gmail.com \
--cc=18955@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=haroogan@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.