From: Ilya Zakharevich <ilya@math.berkeley.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 19989@debbugs.gnu.org
Subject: bug#19989: 25.0.50; Build instructions on Windows
Date: Tue, 3 Mar 2015 13:15:25 -0800 [thread overview]
Message-ID: <20150303211525.GA27909@math.berkeley.edu> (raw)
In-Reply-To: <834mq2qana.fsf@gnu.org>
On Tue, Mar 03, 2015 at 07:00:09PM +0200, Eli Zaretskii wrote:
> > Date: Tue, 3 Mar 2015 08:34:53 -0800
> > From: Ilya Zakharevich <nospam-abuse@ilyaz.org>
> >
> > =======================================================
> >
> > I needed the following changes to build Emacs (when following the
> > instructions in nt/INSTALL):
> > • mingw-get:
> > actually, mingw32-base is not installed by default;
> > I needed to install it by manually marking it in mingw-get.
> > • mingw shell sets path to (essentially) FOO/msys/1.0/mingw/bin (here FOO
> > is the install path), but there is no directory
> > FOO/msys/1.0/mingw
> > what is is
> > FOO/bin
> > So I needed to make a symbolic link (Windows style required) by
> > running
> > mklink /j mingw FOO
> > in FOO/msys/1.0
>
> Thanks.
>
> I suggest to post this to the MinGW mailing list
> <mingw-users@lists.sourceforge.net> first, as what you describe sounds
> like MinGW issues not directly related to building Emacs. If they say
> that this is "as designed", then we will see about adding something to
> nt/INSTALL to work around this.
I tried. They require registration (and I exhaused my abilities to
register already more than a decade ago). If somebody is a member, can
you forward this?
Thanks,
Ilya
prev parent reply other threads:[~2015-03-03 21:15 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 16:34 bug#19989: 25.0.50; Build instructions on Windows Ilya Zakharevich
2015-03-03 17:00 ` Eli Zaretskii
2015-03-03 17:21 ` Eli Zaretskii
2015-03-03 20:30 ` Ilya Zakharevich
2015-03-04 3:42 ` Eli Zaretskii
2015-03-05 21:18 ` Ilya Zakharevich
2015-03-06 8:29 ` Eli Zaretskii
2015-03-06 9:21 ` martin rudalics
2015-03-06 9:59 ` Ilya Zakharevich
2015-03-06 11:16 ` Eli Zaretskii
2015-03-07 1:44 ` Ilya Zakharevich
2015-03-07 9:11 ` Eli Zaretskii
2015-03-08 6:22 ` Ilya Zakharevich
2015-08-15 8:03 ` Eli Zaretskii
2015-08-15 11:22 ` Dani Moncayo
2015-08-15 11:38 ` Dani Moncayo
2015-08-15 12:10 ` Eli Zaretskii
2015-08-15 12:09 ` Eli Zaretskii
2015-08-15 12:24 ` Dani Moncayo
2015-08-15 12:26 ` Eli Zaretskii
2015-08-15 13:39 ` Dani Moncayo
2015-03-06 10:28 ` Eli Zaretskii
2015-03-06 14:13 ` Óscar Fuentes
2015-03-06 14:14 ` Óscar Fuentes
2015-03-06 14:40 ` Eli Zaretskii
2015-03-07 1:47 ` Ilya Zakharevich
2015-03-07 2:04 ` Óscar Fuentes
2015-03-07 9:19 ` Eli Zaretskii
2015-03-06 18:53 ` martin rudalics
2015-03-06 19:27 ` Eli Zaretskii
2015-03-07 9:40 ` martin rudalics
2015-03-07 10:04 ` Eli Zaretskii
2015-03-07 10:28 ` martin rudalics
2015-03-08 6:07 ` Ilya Zakharevich
2015-03-08 10:04 ` martin rudalics
2015-03-08 16:07 ` Ilya Zakharevich
2015-03-06 9:46 ` Ilya Zakharevich
2015-03-06 10:33 ` Eli Zaretskii
2015-03-07 1:37 ` Ilya Zakharevich
2015-03-06 10:08 ` Eli Zaretskii
2015-03-07 1:35 ` Ilya Zakharevich
2015-03-07 9:04 ` Eli Zaretskii
2015-03-08 6:14 ` Ilya Zakharevich
2015-03-08 15:46 ` Eli Zaretskii
2015-03-08 16:04 ` Ilya Zakharevich
2015-03-08 16:59 ` Eli Zaretskii
2015-03-03 21:15 ` Ilya Zakharevich [this message]
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=20150303211525.GA27909@math.berkeley.edu \
--to=ilya@math.berkeley.edu \
--cc=19989@debbugs.gnu.org \
--cc=eliz@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).