all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: lekktu@gmail.com, emacs-devel@gnu.org
Subject: Re: Failure to bootstrap on Windows
Date: Sat, 03 Oct 2015 10:31:52 +0200	[thread overview]
Message-ID: <560F9278.8050101@gmx.at> (raw)
In-Reply-To: <83a8s15es5.fsf@gnu.org>

 >>   >> $ echo $PATH
 >>   >> .:/c/Devel/emacs/build/bin:/mingw/bin:/bin:/c/WINDOWS/system32:/c/WINDOWS:/c/WINDOWS/System32/Wbem:/c/bin64/Git/cmd
 >>                                        ^^^^^^^^^
 >> What is bin:/bin:?
 >
 > No, it's /mingw/bin:bin:.  The separator is the colon, Posix-style.

So mingw is a subdirectory of msys.  Is that the preferred way?  Here
msys is a subdirectory of mingw.

 >>     Do NOT add the MSYS bin directory to your Windows Path!  Only the
 >>     MinGW bin directory should be on Path.
 >
 > That's in the opposite direction.  What I said above is about the PATH
 > seen by MSYS Bash, not the PATH seen by the rest of Windows
 > applications.

What do I do to ensure that "MinGW's bin directory" is "_after_ the MSYS
directories" in MSYS Bash?

martin



  reply	other threads:[~2015-10-03  8:31 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-30  8:29 Failure to bootstrap on Windows Juanma Barranquero
2015-10-01  9:55 ` Eli Zaretskii
2015-10-01 14:07   ` Juanma Barranquero
2015-10-01 16:47     ` Dani Moncayo
2015-10-01 21:34       ` Juanma Barranquero
2015-10-01 17:02     ` Eli Zaretskii
2015-10-01 20:52       ` Juanma Barranquero
2015-10-01 21:01         ` Eli Zaretskii
2015-10-01 21:45           ` Juanma Barranquero
2015-10-02  6:41             ` Eli Zaretskii
2015-10-02  7:13               ` Juanma Barranquero
2015-10-02  8:36                 ` Eli Zaretskii
2015-10-02  9:58                   ` Juanma Barranquero
2015-10-02 10:14                     ` Eli Zaretskii
2015-10-02 10:21                       ` Juanma Barranquero
2015-10-02 15:15             ` Eli Zaretskii
2015-10-02 15:45               ` Juanma Barranquero
2015-10-02 17:47                 ` Eli Zaretskii
2015-10-02 18:48                   ` Juanma Barranquero
2015-10-02 19:07                     ` Eli Zaretskii
2015-10-02 21:49                       ` Juanma Barranquero
2015-10-03  8:35                         ` Eli Zaretskii
2015-10-03 10:01                           ` Eli Zaretskii
2015-10-03 21:17                           ` Juanma Barranquero
2015-10-04  2:53                             ` Juanma Barranquero
2015-10-04  6:56                               ` Eli Zaretskii
2015-10-04 10:07                                 ` Juanma Barranquero
2015-10-04 10:18                                   ` Werner LEMBERG
2015-10-04 11:00                                     ` Eli Zaretskii
2015-10-04 11:48                                     ` Juanma Barranquero
2015-10-04 10:59                                   ` Eli Zaretskii
2015-10-04 11:51                                     ` Juanma Barranquero
2015-10-04 12:02                                       ` Eli Zaretskii
2015-10-04 14:41                                         ` Stephen Leake
2015-10-04 16:56                                           ` Eli Zaretskii
2015-10-04  6:36                             ` Eli Zaretskii
2015-10-02  8:37 ` martin rudalics
2015-10-02  9:37   ` Juanma Barranquero
2015-10-02  9:52     ` martin rudalics
2015-10-02 13:01     ` Stephen Leake
2015-10-02 13:32       ` Juanma Barranquero
2015-10-02 13:55     ` Eli Zaretskii
2015-10-02 15:02       ` Juanma Barranquero
2015-10-02 15:20         ` Eli Zaretskii
2015-10-02 15:31           ` Juanma Barranquero
2015-10-02 16:23           ` martin rudalics
2015-10-02 18:03             ` Eli Zaretskii
2015-10-03  8:31               ` martin rudalics [this message]
2015-10-03 10:00                 ` Eli Zaretskii
2015-10-02 10:04   ` 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=560F9278.8050101@gmx.at \
    --to=rudalics@gmx.at \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@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.