GNU bug report logs -
#18765
Emacs 24.4 release candidate 1: "term/w32-win.el" is missing on Windows
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 18765 in the body.
You can then email your comments to 18765 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#18765
; Package
emacs
.
(Sat, 18 Oct 2014 17:32:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
"Yanning Du" <duyanning <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Sat, 18 Oct 2014 17:32:03 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Platform: Windows 7
Emacs version: Emacs 24.4 release candidate 1
I used the following commands to build and install Emacs 24.4 release candidate 1:
/f/build-emacs/emacs-24.3.94$ CFLAGS='-I/f/build-emacs/libxpm-3.5.8-w32-src/include -I/f/build-emacs/libxpm-3.5.8-w32-src/src' ./configure --prefix=/f/myemacs-24.3.94
/f/build-emacs/emacs-24.3.94$ make
/f/build-emacs/emacs-24.3.94$ make install
When it is finished, I run emacs -Q
However, a message box is poped up saying:
====================Emacs Abort Dialog ======================
The Emacs Windows initialization file "term/w32-win.el" could not be found in your Emacs installation. Emacs checked the following directories for this file:
("f:/myemacs-24.3.94/site-lisp" "F:/myemacs-24.3.94/../site-lisp" "F:/myemacs-24.3.94/lisp" "F:/myemacs-24.3.94/leim")
When Emacs cannot find this file, it usually means that it was not installed properly, or its distribution file was not unpacked properly.
See the README.W32 file in the top-level Emacs directory for more information.
=======================================================
Actually, w32-win.el EXISTS in my system, but it under F:\myemacs-24.3.94\share\emacs\24.3.94\lisp\term\
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#18765
; Package
emacs
.
(Sat, 18 Oct 2014 17:46:01 GMT)
Full text and
rfc822 format available.
Message #8 received at 18765 <at> debbugs.gnu.org (full text, mbox):
> Date: Sat, 18 Oct 2014 22:55:40 +0800
> From: "Yanning Du" <duyanning <at> gmail.com>
>
> I used the following commands to build and install Emacs 24.4 release candidate 1:
> /f/build-emacs/emacs-24.3.94$ CFLAGS='-I/f/build-emacs/libxpm-3.5.8-w32-src/include -I/f/build-emacs/libxpm-3.5.8-w32-src/src' ./configure --prefix=/f/myemacs-24.3.94
> /f/build-emacs/emacs-24.3.94$ make
> /f/build-emacs/emacs-24.3.94$ make install
>
> When it is finished, I run emacs -Q
> However, a message box is poped up saying:
> ====================Emacs Abort Dialog ======================
> The Emacs Windows initialization file "term/w32-win.el" could not be found in your Emacs installation. Emacs checked the following directories for this file:
>
> ("f:/myemacs-24.3.94/site-lisp" "F:/myemacs-24.3.94/../site-lisp" "F:/myemacs-24.3.94/lisp" "F:/myemacs-24.3.94/leim")
>
> When Emacs cannot find this file, it usually means that it was not installed properly, or its distribution file was not unpacked properly.
> See the README.W32 file in the top-level Emacs directory for more information.
> =======================================================
>
> Actually, w32-win.el EXISTS in my system, but it under F:\myemacs-24.3.94\share\emacs\24.3.94\lisp\term\
Please show the contents of F:/build-emacs/emacs-24.3.94/src/epaths.h.
Also, please make sure you don't have any of the following variables
set, neither in the environment nor in the Registry:
PATH_LOADSEARCH
PATH_SITELOADSEARCH
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#18765
; Package
emacs
.
(Sat, 18 Oct 2014 17:48:01 GMT)
Full text and
rfc822 format available.
Message #11 received at 18765 <at> debbugs.gnu.org (full text, mbox):
> Date: Sat, 18 Oct 2014 20:44:39 +0300
> From: Eli Zaretskii <eliz <at> gnu.org>
> Cc: 18765 <at> debbugs.gnu.org
>
> Also, please make sure you don't have any of the following variables
> set, neither in the environment nor in the Registry:
>
> PATH_LOADSEARCH
> PATH_SITELOADSEARCH
Please add emacs_dir variable to that list.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#18765
; Package
emacs
.
(Sun, 19 Oct 2014 02:48:01 GMT)
Full text and
rfc822 format available.
Message #14 received at 18765 <at> debbugs.gnu.org (full text, mbox):
[Please keep the bug address in the CC list.]
> From: "Yanning Du" <duyanning <at> gmail.com>
> Date: Sun, 19 Oct 2014 10:18:02 +0800
>
> The contents of F:/build-emacs/emacs-24.3.94/src/epaths.h:
>
> #define PATH_LOADSEARCH "%emacs_dir%/share/emacs/24.3.94/lisp"
> #define PATH_SITELOADSEARCH "%emacs_dir%/share/emacs/24.3.94/site-lisp;%emacs_dir%/share/emacs/site-lisp"
> #define PATH_DUMPLOADSEARCH "f:/build-emacs/emacs-24.3.94/lisp"
> #define PATH_EXEC "%emacs_dir%/libexec/emacs/24.3.94/i686-pc-mingw32"
> #define PATH_DATA "%emacs_dir%/share/emacs/24.3.94/etc"
> #define PATH_BITMAPS ""
> #define PATH_DOC "%emacs_dir%/share/emacs/24.3.94/etc"
> #define PATH_INFO "%emacs_dir%/share/info"
> #define PATH_GAME "%emacs_dir%/var/games/emacs"
> #define PATH_X_DEFAULTS ""
>
>
> I have neither PATH_LOADSEARCH nor PATH_SITELOADSEARCH
> defined in my environment and registry.
>
> Although emacs_dir is defined in registry, I think it is added
> by former emacs 24.3 automatically when it runs.
Please remove it from the registry and try again.
Also, how did you invoke Emacs after building it? From the command
prompt (and if so, which shell), from a desktop shortcut, Start->Run
dialog, something else?
> Before Emacs 24.4, I used configure.bat to build and it is OK.
> However when I were using it to build emacs 24.4, it said:
>
> *** THIS METHOD OF BUILDING EMACS IS NO LONGER SUPPORTED. **
> *** INSTEAD, FOLLOW THE INSTRUCTIONS FROM INSTALL. **
>
> So I use the new method.
That is the correct method of building Emacs now.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#18765
; Package
emacs
.
(Sun, 19 Oct 2014 13:36:02 GMT)
Full text and
rfc822 format available.
Message #17 received at 18765 <at> debbugs.gnu.org (full text, mbox):
[Once again, PLEASE keep the bug address on the CC list.]
> From: "Yanning Du" <duyanning <at> gmail.com>
> Date: Sun, 19 Oct 2014 10:57:14 +0800
>
> I removed emacs_dir from the registry and ran emacs, I got the same message box.
> Should I rebuild emacs after removing emacs_dir from the registry?
I don't know yet, because what you report includes some strange
details, see below.
> I ran emacs 24.4 using runemacs.exe from command prompt (cmd.exe).
Please try running emacs.exe from F:\myemacs-24.3.94\bin directly from
the cmd.exe prompt. Does that show the same abort dialog, or does it
run normally?
Here are the questions I have regarding your report:
> Emacs version: Emacs 24.4 release candidate 1
>
> I used the following commands to build and install Emacs 24.4 release candidate 1:
> /f/build-emacs/emacs-24.3.94$ CFLAGS='-I/f/build-emacs/libxpm-3.5.8-w32-src/include -I/f/build-emacs/libxpm-3.5.8-w32-src/src' ./configure --prefix=/f/myemacs-24.3.94
> /f/build-emacs/emacs-24.3.94$ make
> /f/build-emacs/emacs-24.3.94$ make install
You say you've built Emacs 24.4 release candidate 1, but the build
directory and the --prefix argument seem to say it's 24.3.94, a
pretest. Likewise, your src/epaths.h file says it's a 24.3.94
pretest:
> #define PATH_LOADSEARCH "%emacs_dir%/share/emacs/24.3.94/lisp"
> #define PATH_SITELOADSEARCH "%emacs_dir%/share/emacs/24.3.94/site-lisp;%emacs_dir%/share/emacs/site-lisp"
> #define PATH_DUMPLOADSEARCH "f:/build-emacs/emacs-24.3.94/lisp"
> #define PATH_EXEC "%emacs_dir%/libexec/emacs/24.3.94/i686-pc-mingw32"
> #define PATH_DATA "%emacs_dir%/share/emacs/24.3.94/etc"
> #define PATH_BITMAPS ""
> #define PATH_DOC "%emacs_dir%/share/emacs/24.3.94/etc"
> #define PATH_INFO "%emacs_dir%/share/info"
> #define PATH_GAME "%emacs_dir%/var/games/emacs"
> #define PATH_X_DEFAULTS ""
So which version did you build, exactly?
Also, did you put the F:\myemacs-24.3.94\bin on your PATH?
In any case, the directories where Emacs claims to have looked for
term/w32-win.el, i.e.
("f:/myemacs-24.3.94/site-lisp" "F:/myemacs-24.3.94/../site-lisp" "F:/myemacs-24.3.94/lisp" "F:/myemacs-24.3.94/leim")
correspond to the old build and install method, the one you used to do
using nt/configure.bat. So my first guess would be that you invoked
an old emacs.exe, which still tries to look for its files in the old
place. Please see what is the full path to emacs.exe that is running
when you are shown the abort dialog (you can do this using specialized
utilities, such as the Process Explorer from SysInternals, whch show
various properties of the running process).
Reply sent
to
Eli Zaretskii <eliz <at> gnu.org>
:
You have taken responsibility.
(Tue, 21 Oct 2014 17:46:01 GMT)
Full text and
rfc822 format available.
Notification sent
to
"Yanning Du" <duyanning <at> gmail.com>
:
bug acknowledged by developer.
(Tue, 21 Oct 2014 17:46:02 GMT)
Full text and
rfc822 format available.
Message #22 received at 18765-done <at> debbugs.gnu.org (full text, mbox):
> From: "Yanning Du" <duyanning <at> gmail.com>
> Date: Wed, 22 Oct 2014 00:07:33 +0800
>
> I deleted all values under 'HKEY_CURRENT_USER\Software\GNU\Emacs ' excepting HOME.
> Everything seems OK now.
> Thank you, Eli.
>
> I suspect that these values were added by a pretest version, may be emacs-24.3.94.
OK, I'm closing the bug.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#18765
; Package
emacs
.
(Tue, 21 Oct 2014 20:14:02 GMT)
Full text and
rfc822 format available.
Message #25 received at 18765 <at> debbugs.gnu.org (full text, mbox):
This is then http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16429#43
If would be good if the MS Windows build could be robust against these
issues.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#18765
; Package
emacs
.
(Tue, 21 Oct 2014 20:24:02 GMT)
Full text and
rfc822 format available.
Message #28 received at 18765 <at> debbugs.gnu.org (full text, mbox):
> This is then http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16429#43
>
> If would be good if the MS Windows build could be robust against
> these issues.
What MS Windows build?
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#18765
; Package
emacs
.
(Tue, 21 Oct 2014 20:32:02 GMT)
Full text and
rfc822 format available.
Message #31 received at 18765 <at> debbugs.gnu.org (full text, mbox):
> From: Glenn Morris <rgm <at> gnu.org>
> Date: Tue, 21 Oct 2014 16:13:07 -0400
>
>
> This is then http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16429#43
>
> If would be good if the MS Windows build could be robust against these
> issues.
If you know how, please suggest a method.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#18765
; Package
emacs
.
(Tue, 21 Oct 2014 21:16:03 GMT)
Full text and
rfc822 format available.
Message #34 received at 18765 <at> debbugs.gnu.org (full text, mbox):
Eli Zaretskii wrote:
> If you know how, please suggest a method.
Either a command-line option meaning "ignore the registry", which gets
added to the Makefile Emacs flags; or, if environment variables trump
the registry, change it so that empty environment variables mean "use
the defaults" (right now they just break things), and change the
Makefiles to set empty environment variables rather than unsetting them
like they do now (seemed not straightforward last time I looked).
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#18765
; Package
emacs
.
(Wed, 22 Oct 2014 02:50:03 GMT)
Full text and
rfc822 format available.
Message #37 received at 18765 <at> debbugs.gnu.org (full text, mbox):
> From: Glenn Morris <rgm <at> gnu.org>
> Cc: 18765 <at> debbugs.gnu.org, 16429 <at> debbugs.gnu.org
> Date: Tue, 21 Oct 2014 17:15:47 -0400
>
> Eli Zaretskii wrote:
>
> > If you know how, please suggest a method.
>
> Either a command-line option meaning "ignore the registry", which gets
> added to the Makefile Emacs flags
How does this help when the user just invokes "emacs" with no options,
as in this case?
> or, if environment variables trump the registry, change it so that
> empty environment variables mean "use the defaults" (right now they
> just break things), and change the Makefiles to set empty
> environment variables rather than unsetting them like they do now
> (seemed not straightforward last time I looked).
Why are you talking about the Makefile? The problem ws not in
invoking Emacs from the Makefile, it was in interactive usage after
the build is done (in bug #18765).
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#18765
; Package
emacs
.
(Wed, 22 Oct 2014 04:44:02 GMT)
Full text and
rfc822 format available.
Message #40 received at 18765 <at> debbugs.gnu.org (full text, mbox):
Eli Zaretskii wrote:
> Why are you talking about the Makefile? The problem ws not in
> invoking Emacs from the Makefile, it was in interactive usage after
> the build is done (in bug #18765).
Oh, durr, I wasn't paying attention, sorry.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Wed, 19 Nov 2014 12:24:04 GMT)
Full text and
rfc822 format available.
This bug report was last modified 10 years and 276 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.