From: Ilya Zakharevich <ilya@math.berkeley.edu>
To: martin rudalics <rudalics@gmx.at>
Cc: 19989@debbugs.gnu.org
Subject: bug#19989: 25.0.50; Build instructions on Windows
Date: Fri, 6 Mar 2015 01:59:52 -0800 [thread overview]
Message-ID: <20150306095952.GA11017@math.berkeley.edu> (raw)
In-Reply-To: <54F971AD.2050907@gmx.at>
On Fri, Mar 06, 2015 at 10:21:49AM +0100, martin rudalics wrote:
> Setting up mingw without mingw-get from scratch (resolving all the
> necessary dependencies) looks like it could take at least a week here.
> Maybe I'm wrong but it appears that every DL and installation step has
> to be prepared carefully wrt overwriting (or not) previously installed
> libraries.
>
> Using mingw-get (which I did) is complicated as well if you want to
> avoid falling into one of the traps mentioned in this thread.
I think building Emacs stole about 10 hours of my active time.
However, I must mention that the MAIN problem was:
A) apparently, the download and build instructions changes not so
long ago, so what google finds are obsolete irrelevant
instructions.
B) Since I got many different versions of Emacs build tree
downloaded, I might have mixed up all the BAR/nt/INSTALL. Do not
know how did it happen EXACTLY, but for several rounds I was
thinking I MUST run
nt/configure.bat
The warning which nt/configure.bat gives is not specific enough (at
least when shown on background of all the [wrong] info found by googling):
echo ****************************************************************
echo *** THIS METHOD OF BUILDING EMACS IS NO LONGER SUPPORTED. **
echo *** INSTEAD, FOLLOW THE INSTRUCTIONS FROM INSTALL. **
echo ****************************************************************
--------------------------------------------
I cannot be sure, but I suspect that if it would show an extra line:
**** The current way is to install MSYS and MINGW, ****
**** and run the top-level configure script. ****
this might have saved me about half of these 10 hours. (But it might
have been my very personal way to confuse myself, and this extra
message won’t be so useful for other people.)
Ilya
next prev parent reply other threads:[~2015-03-06 9:59 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 [this message]
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
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=20150306095952.GA11017@math.berkeley.edu \
--to=ilya@math.berkeley.edu \
--cc=19989@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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).