From: Jason Rumney <jasonr@gnu.org>
Cc: Juanma Barranquero <lekktu@gmail.com>, emacs-devel@gnu.org
Subject: Re: W32 version crashes on C-g
Date: Fri, 17 Mar 2006 16:07:58 +0000 [thread overview]
Message-ID: <441ADEDE.5040706@gnu.org> (raw)
In-Reply-To: <m3lkv9f7oa.fsf@kfs-l.imdomain.dk>
Kim F. Storm wrote:
> Checking whether 'gcc' is available...
> Checking whether gcc requires '-mno-cygwin'...
> The system cannot find the file specified.
> Checking whether W32 API headers are too old...
>
> C:\gnu\devel\nt>gcc -mno-cygwin -c junk.c
> gcc: installation problem, cannot exec `cc1': No such file or directory
>
> Configure failed.
>
It seems your installation of gcc is incomplete.
> 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.
>
The problem with putting such advice in INSTALL is that it quickly
becomes out of date, as URLs change and the versions found on these
third party sites are upgraded.
next prev parent reply other threads:[~2006-03-17 16:07 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=441ADEDE.5040706@gnu.org \
--to=jasonr@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.