From: Harald Maier <harald@maierh.de>
Subject: Re: Fatal error when trying to run emacs 21.3 on win2k
Date: Sat, 14 Feb 2004 17:30:25 +0100 [thread overview]
Message-ID: <m3k72pzkri.fsf@ate.maierh> (raw)
In-Reply-To: 68945b72.0402140553.47234291@posting.google.com
groupsuser@yahoo.com (David) writes:
> I'm trying to upgrade from emacs 20.7 to emacs 21.3. (BTW, it's not
> clear to me if version 21.3 is valid -- according to
> http://ftp.gnu.org/pub/gnu/windows/emacs/21.3/emacs-21.3-fullbin-i386.tar.gz.back-RSN.README
> from 23Oct2003 it's not valid, but nevertheless the files appear
> ready for download at
> http://ftp.gnu.org/pub/gnu/emacs/windows/emacs-21.3-fullbin-i386.tar.gz
> from 26Jan2004). I downloaded from the abovementioned address, ran
> gunzip-1.2.4-i386, tar-1.11.2a, and addpm. All seemed to execute
> okay. I now have 2 subdirectories in C:\emacs, emacs-20.7 and
> emacs-21.3. When I try to run emacs.exe from
> C:\emacs\emacs-21.3\bin, I get an "Emacs Abort Dialog" window
> stating that a fatal error has occured. Then I get a "Program
> Error" window stating that emacs.exe has generated errors and will
> be closed by Windows.
Yes, you are right, the current version of emacs on the ftp.gnu.org
server has the described problem. The binaries will be replaced but
this can take some time. Please look for other downloads. The places
are posted here. E.g.:
http://www.google.de/groups?hl=de&lr=&ie=UTF-8&oe=UTF-8&selm=u65f6tiog.fsf%40noniq.at
If you want to compile emacs by yourself you need either MSVC or you
can do it with cygwin gcc. But for emacs-21.3 and for the latest
cygwin gccs you need to a patch. This patch is too missing in the
above mentioned version on ftp.gnu.org. You may find additional info
here for under:
help-emacs-windows@gnu.org
Harald
prev parent reply other threads:[~2004-02-14 16:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-14 13:53 Fatal error when trying to run emacs 21.3 on win2k David
2004-02-14 16:30 ` Harald Maier [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=m3k72pzkri.fsf@ate.maierh \
--to=harald@maierh.de \
/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.
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).