unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: W32 version crashes on C-g
Date: Sat, 18 Mar 2006 12:52:12 +0200	[thread overview]
Message-ID: <uslpgvxcz.fsf@gnu.org> (raw)
In-Reply-To: <m3lkv9f7oa.fsf@kfs-l.imdomain.dk> (storm@cua.dk)

> From: storm@cua.dk (Kim F. Storm)
> Date: Fri, 17 Mar 2006 15:49:09 +0100
> Cc: emacs-devel@gnu.org
> 
> So you lost me there...  I just installed MSYS and MINGW, and now
> you're telling me to run stuff in COMMAND.COM ?

You don't need MSYS, just MinGW.

The Makefile's produced by nt/configure.bat will run both with and
without a Unixy shell.  And in any case, there's no need to invoke
configure.bat from a Unixy shell, since it's a batch file.  (In fact,
some ports of sh.exe will not be able to run batch files at all.)

> C:\gnu\devel\nt>gcc  -mno-cygwin -c junk.c
> gcc: installation problem, cannot exec `cc1': No such file or directory

Your GCC installation is broken or incomplete.

> I tried to look at nt/INSTALL, and rather than giving
> ONE CLEAR way to build it, it gives an utterly complex
> mix of basic CMD.COM, Cygwin, and MinGW stuff that may
> work in various combinations.

I understand that you were in a hurry and mildly annoyed, and in that
condition too complex installation instructions may cause a lot of
grief.  But please look closer at nt/INSTALL: the ``complex mix'' is
described at the beginning, and after that you have sections labeled
"Confoguring", "Building", and "Installing" that describe the way to
build and install Emacs.

> Would someone like to work on a simple, step-by-step
> guide for building this using ONE tool-kit (e.g. MinGW),
> tell _exactly_ where to find the right versions of those tools,
> libaries, etc. it would be nice.

nt/INSTALL assumes that you already have a working development
environment, and so it doesn't tell how to set up such an environment.
I don't object to adding such info (probably near the end, so that it
stays out of the way of the impatient ;-), but please understand that
you were trying to climb a very steep learning curve, hoping you will
be able to do that in about 5 seconds.  It's just not so easy on
Windows.

  parent reply	other threads:[~2006-03-18 10:52 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-17 10:41 W32 version crashes on C-g Kim F. Storm
2006-03-17 11:46 ` Eric Lilja
2006-03-17 12:07 ` Eli Zaretskii
2006-03-17 12:28   ` Kim F. Storm
2006-03-17 12:32 ` Juanma Barranquero
2006-03-17 14:04   ` Kim F. Storm
2006-03-17 14:20     ` Juanma Barranquero
2006-03-17 14:49       ` Kim F. Storm
2006-03-17 16:07         ` Jason Rumney
2006-03-17 16:08         ` Lennart Borgman
2006-03-18  1:13           ` Kim F. Storm
2006-03-18  7:51             ` Lennart Borgman
2006-03-18 11:29             ` Eli Zaretskii
2006-03-17 16:52         ` Juanma Barranquero
2006-03-17 17:06           ` Drew Adams
2006-03-17 18:00           ` Lennart Borgman
2006-03-17 23:27             ` Juanma Barranquero
2006-03-18  0:01               ` Lennart Borgman
2006-03-18  5:49                 ` Juanma Barranquero
2006-03-18  7:48                   ` Lennart Borgman
2006-03-18 12:46                     ` Juanma Barranquero
2006-03-17 18:30           ` Binaries for W32 (was: W32 version crashes on C-g) Reiner Steib
2006-03-17 18:42             ` Drew Adams
2006-03-17 18:56               ` Lennart Borgman
2006-03-17 18:58                 ` Drew Adams
2006-03-20 18:32                   ` Drew Adams
2006-03-21 10:29                     ` Juanma Barranquero
2006-03-22 15:16                       ` Mathias Dahl
2006-03-25 10:15                       ` Eli Zaretskii
2006-03-18  1:21           ` W32 version crashes on C-g Kim F. Storm
2006-03-18  6:00             ` Juanma Barranquero
2006-03-18 11:42               ` Eli Zaretskii
2006-03-18 12:45                 ` Juanma Barranquero
2006-03-18 15:42                   ` Eli Zaretskii
2006-03-18 16:55                     ` Juanma Barranquero
2006-03-18 17:59                       ` Eli Zaretskii
2006-03-18 20:38                         ` Lennart Borgman
2006-03-18 21:42                           ` Juanma Barranquero
2006-03-18 20:46                   ` Lennart Borgman
2006-03-19  1:32               ` Kim F. Storm
2006-03-21 10:35                 ` Juanma Barranquero
2006-03-21 12:43                   ` Kim F. Storm
2006-03-21 15:22                     ` Juanma Barranquero
2006-03-18 10:52         ` Eli Zaretskii [this message]
2006-03-19  1:44           ` Kim F. Storm
2006-03-18 16:23         ` Eli Zaretskii
2006-03-18 17:14           ` Eric Hanchrow
2006-03-18 17:15           ` Chong Yidong
2006-03-18 18:10             ` Eli Zaretskii
2006-03-18 18:59             ` Jason Rumney
2006-03-18 19:11               ` Chong Yidong
2006-03-18 22:38                 ` Eli Zaretskii
2006-03-19  0:46           ` Kim F. Storm
2006-03-18 16:27         ` Eric Hanchrow
2006-03-18 17:56           ` Eli Zaretskii
2006-03-18 16:29         ` Eric Hanchrow
2006-03-18 18:19           ` Eli Zaretskii
2006-03-18 19:04           ` Jason Rumney
2006-03-18 10:40     ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2006-03-17 12:58 LENNART BORGMAN

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=uslpgvxcz.fsf@gnu.org \
    --to=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).