From: Dani Moncayo <dmoncayo@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: Building Emacs from a new MinGW environment
Date: Tue, 17 Sep 2013 10:17:38 +0200 [thread overview]
Message-ID: <CAH8Pv0g_2ebX1q+dTxP3d1nOwm=5seHC-Oezwa-CA47mBUtPkQ@mail.gmail.com> (raw)
In-Reply-To: <83k3ifq5o5.fsf@gnu.org>
> Change this:
>
> case "${srcdir}" in
> [[\\/]]* | ?:[[\\/]]*) ;;
>
> into this:
>
> case "${srcdir}" in
> [[\\/]]* | ?:[[\\/]]*)
> test "$MSYSTEM" = "MINGW32" && srcdir=`(cd "$srcdir"; pwd -W)`
> ;;
>
> This fix, if it works, is better, since it will fix also the stuff
> that gets written into .gdbinit file in the build directory (it didn't
> work for you because an MSYS file name was written there, and the
> MinGW build of GDB doesn't grok that).
This does't work in my case, because at that point, "${srcdir}"
contains the relative path "../emacs.git", not something like
"/c/whatever" or "c:/whatever".
I think that the right fix is to replace *all* the treatment of
patterns like the above ("/c/whatever" or "c:/whatever") with logic
based on the "pwd -W" feature of MSYS.
IOW, an MSYS path doesn't have to match none of the above patterns, so
the only reliable way of getting a Windows-native path is with "pwd
-W".
Therefore, things line "msys_to_w32", "msys_lisppath_to_w32" should be
replaced with the above criteria.
--
Dani Moncayo
next prev parent reply other threads:[~2013-09-17 8:17 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 18:38 Building Emacs from a new MinGW environment Dani Moncayo
2013-08-26 19:38 ` Eli Zaretskii
2013-08-26 20:08 ` Dani Moncayo
2013-09-13 14:31 ` Dani Moncayo
2013-09-14 9:32 ` Eli Zaretskii
2013-09-14 9:41 ` Dani Moncayo
2013-09-14 10:07 ` Eli Zaretskii
2013-09-14 14:25 ` Dani Moncayo
2013-09-14 14:50 ` Eli Zaretskii
2013-09-14 15:42 ` Dani Moncayo
2013-09-14 16:10 ` Eli Zaretskii
2013-09-14 16:34 ` Dani Moncayo
2013-09-14 17:18 ` Eli Zaretskii
2013-09-14 19:57 ` Dani Moncayo
2013-09-14 20:56 ` Eli Zaretskii
2013-09-14 21:19 ` Dani Moncayo
2013-09-14 22:30 ` Dani Moncayo
2013-09-15 9:35 ` Eli Zaretskii
2013-09-15 9:28 ` Eli Zaretskii
2013-09-16 16:48 ` Dani Moncayo
2013-09-16 17:37 ` Eli Zaretskii
2013-09-16 19:25 ` Dani Moncayo
2013-09-16 19:40 ` Eli Zaretskii
2013-09-16 19:44 ` Dani Moncayo
2013-09-16 20:19 ` Eli Zaretskii
2013-09-17 7:16 ` Eli Zaretskii
2013-09-17 8:17 ` Dani Moncayo [this message]
2013-09-17 8:30 ` Eli Zaretskii
2013-09-17 16:09 ` Dani Moncayo
2013-09-17 16:17 ` Glenn Morris
2013-09-17 17:27 ` Eli Zaretskii
2013-09-17 20:29 ` Dani Moncayo
2013-09-18 7:46 ` Eli Zaretskii
2013-09-18 9:32 ` Dani Moncayo
2013-09-18 10:00 ` Eli Zaretskii
2013-09-18 10:38 ` Dani Moncayo
2013-09-18 11:21 ` Eli Zaretskii
2013-09-18 12:39 ` Dani Moncayo
2013-09-18 12:31 ` Dani Moncayo
2013-09-18 13:14 ` Eli Zaretskii
2013-09-18 16:51 ` Dani Moncayo
2013-09-18 19:20 ` Eli Zaretskii
2013-09-19 22:56 ` Dani Moncayo
2013-09-20 8:14 ` Eli Zaretskii
2013-09-20 9:29 ` Andy Moreton
2013-09-20 11:08 ` Dani Moncayo
2013-09-20 11:21 ` Eli Zaretskii
2013-09-20 12:22 ` Dani Moncayo
2013-09-20 12:30 ` Dani Moncayo
2013-09-20 13:16 ` Eli Zaretskii
2013-09-20 13:12 ` Eli Zaretskii
2013-09-20 14:12 ` Eli Zaretskii
2013-09-20 15:05 ` Dani Moncayo
2013-09-18 10:46 ` Andy Moreton
2013-09-18 11:24 ` Eli Zaretskii
2013-09-18 12:44 ` Sean Sieger
2013-09-18 13:16 ` Eli Zaretskii
2013-09-18 13:19 ` Sean Sieger
2013-09-18 14:33 ` Eli Zaretskii
2013-09-18 13:21 ` Andy Moreton
2013-09-18 14:45 ` Eli Zaretskii
2013-09-18 20:51 ` Andy Moreton
2013-09-19 8:45 ` Eli Zaretskii
2013-09-19 8:56 ` Dani Moncayo
2013-09-19 9:38 ` Eli Zaretskii
2013-09-19 10:04 ` Dani Moncayo
2013-09-19 10:11 ` Eli Zaretskii
2013-11-09 14:47 ` Dani Moncayo
2013-11-10 16:32 ` Dani Moncayo
2013-11-12 2:56 ` Glenn Morris
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='CAH8Pv0g_2ebX1q+dTxP3d1nOwm=5seHC-Oezwa-CA47mBUtPkQ@mail.gmail.com' \
--to=dmoncayo@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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).