From: Alexander Shukaev <haroogan@gmail.com>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: 18955@debbugs.gnu.org
Subject: bug#18955: Makefile:382: recipe for target 'src' failed
Date: Sun, 9 Nov 2014 21:25:38 +0100 [thread overview]
Message-ID: <CAKu-7WwdNedxA1HzTDS8DjEpmFkDDO8V8XqsbgG=CWc5tKeW+w@mail.gmail.com> (raw)
In-Reply-To: <83sihsnn9y.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 740 bytes --]
>
> 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.
>
These are out of the scope right now. You are actually not supposed to
pass them outside MSYS2 Shells... Nevertheless, even these ones can be
dealt with in future perspective.
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:".
Absolute paths which are present everywhere in the daily workflow, not only
during builds, but for instance by invoking Emacs from MSYS/Cygwin shell
and passing paths to it, should definitely be supported, and it is as easy
as my proposal.
[-- Attachment #2: Type: text/html, Size: 1323 bytes --]
next prev parent reply other threads:[~2014-11-09 20:25 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
2014-11-09 20:15 ` Eli Zaretskii
2014-11-09 20:25 ` Alexander Shukaev [this message]
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
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-7WwdNedxA1HzTDS8DjEpmFkDDO8V8XqsbgG=CWc5tKeW+w@mail.gmail.com' \
--to=haroogan@gmail.com \
--cc=18955@debbugs.gnu.org \
--cc=dmoncayo@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).