From: Dieter Deyke <deyke@comcast.net>
Cc: emacs-pretest-bug@gnu.org, emacs-devel@gnu.org
Subject: Re: old bootstrap error emerges again
Date: Sat, 18 Mar 2006 12:55:35 -0700 [thread overview]
Message-ID: <ud5gj5xzc.fsf@comcast.net> (raw)
In-Reply-To: <uu09vvdtb.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 18 Mar 2006 19:54:24 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Dieter Deyke <deyke@comcast.net>
>> Cc: emacs-pretest-bug@gnu.org, emacs-devel@gnu.org
>> Date: Sat, 18 Mar 2006 09:22:56 -0700
>>
>> I am seeing the "DOC" error too.
>> My setup: english Windows XP Pro, MinGW-3.1.0-1, cygwin tool set, no msys.
>> Logfile:
>> [...]
>> In toplevel form:
>> url/vc-dav.el:29:1:Error: Cannot open doc string file "c:/Users/deyke/emacs-build/work/etc/DOC"
>> make[1]: *** [compile-SH] Error 1
>> make[1]: Leaving directory `C:/Users/deyke/emacs-build/work/lisp'
>> make: *** [bootstrap-gmake] Error 2
>
> Thanks, this gives me something that I can work with.
>
> Here's the problem: Emacs shouldn't even look for the file named DOC,
> it should look for DOC-X. This is because loadup.el has this
> fragment:
>
> (if (memq system-type '(ms-dos windows-nt))
> (setq name (expand-file-name
> (if (fboundp 'x-create-frame) "DOC-X" "DOC") "../etc"))
> (setq name (concat (expand-file-name "../etc/DOC-") name))
> (if (file-exists-p name)
> (delete-file name))
> (copy-file (expand-file-name "../etc/DOC") name t))
> (Snarf-documentation (file-name-nondirectory name)))
>
> So, on Windows, since x-create-frame is bound, it calls
> Snarf-documentation with the argument "DOC-X". Snarf-documentation
> then records this name in the variable internal-doc-file-name, and
> that name is dumped in emacs.exe. So when byte-compiling for some
> reason calls for a doc file, Emacs should look for DOC-X.
>
> Can you see where the above breaks on your system? In particular,
> when does Vdoc_file_name (defined in doc.c) gets assigned the file
> name which ends with "DOC", not "DOC-X"?
>
> Thanks.
I'm not sure on how to debug this. Let me start to point out that
there were 3 errors about missing DOC, but the first 2 were not fatal:
...
In toplevel form:
url/url-dav.el:36:1:Error: Cannot open doc string file "c:/Users/deyke/emacs-build/work/etc/DOC"
Compiling url/url-dired.el
Wrote c:/Users/deyke/emacs-build/work/lisp/url/url-dired.elc
Compiling url/url-expand.el
Wrote c:/Users/deyke/emacs-build/work/lisp/url/url-expand.elc
Compiling url/url-file.el
...
In toplevel form:
url/url-handlers.el:243:1:Error: Cannot open doc string file "c:/Users/deyke/emacs-build/work/etc/DOC"
Compiling url/url-history.el
Wrote c:/Users/deyke/emacs-build/work/lisp/url/url-history.elc
Compiling url/url-http.el
...
In toplevel form:
url/vc-dav.el:29:1:Error: Cannot open doc string file "c:/Users/deyke/emacs-build/work/etc/DOC"
make[1]: *** [compile-SH] Error 1
make[1]: Leaving directory `C:/Users/deyke/emacs-build/work/lisp'
make: *** [bootstrap-gmake] Error 2
Second, after that build stopped, a find | grep DOC came up empty, so
if anything would expect to find DOC-X, there was none to be found.
Next I probed loadup.el:
system-type --> windows-nt
(fboundp 'x-create-frame) --> t
(setq name (expand-file-name (if (fboundp 'x-create-frame) "DOC-X" "DOC") "../etc")) --> "c:/Users/deyke/emacs-build/etc/DOC-X"
Finally, this is my current work-aound, which seems to give me a
working emacs, although I do not know if the DOC strings are all OK:
cd work/nt
call configure.bat --with-gcc --no-debug --no-cygwin --cflags -IC:/Users/deyke/emacs-build/include --prefix C:/emacs
make bootstrap
REM The last command will have failed with errors, finish the job
cd /d "%basedir%\work\lib-src"
make DOC
copy DOC ..\etc\DOC
cd /d "%basedir%\work\nt"
make
cd /d "%basedir%\work\lisp"
make recompile EMACS=../src/oo-spd/i386/emacs
cd /d "%basedir%\work\nt"
make info
So, could you please guide me in what I have to do to debug this?
Thanks,
--
Dieter Deyke
mailto:deyke@comcast.net mailto:deyke@gmx.net mailto:deyke@yahoo.com
Vs lbh pna ernq guvf, lbh unir jnl gbb zhpu gvzr.
next prev parent reply other threads:[~2006-03-18 19:55 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-17 16:35 old bootstrap error emerges again Zhang Wei
2006-03-18 11:09 ` Eli Zaretskii
2006-03-18 11:59 ` Zhang Wei
2006-03-18 12:55 ` Herbert Euler
2006-03-18 15:49 ` Eli Zaretskii
2006-03-19 1:59 ` Herbert Euler
2006-03-19 4:27 ` Eli Zaretskii
2006-03-18 15:35 ` Eli Zaretskii
2006-03-18 16:22 ` Dieter Deyke
2006-03-18 17:54 ` Eli Zaretskii
2006-03-18 19:55 ` Dieter Deyke [this message]
2006-03-18 21:24 ` Jason Rumney
2006-03-18 21:45 ` Dieter Deyke
2006-03-18 22:55 ` Eli Zaretskii
2006-03-19 0:59 ` Dieter Deyke
2006-03-19 4:37 ` Eli Zaretskii
2006-03-19 14:44 ` Dieter Deyke
2006-03-19 19:14 ` Eli Zaretskii
2006-03-19 20:56 ` Dieter Deyke
2006-03-19 21:19 ` Dieter Deyke
2006-03-25 13:57 ` Eli Zaretskii
2006-03-25 15:54 ` Dieter Deyke
2006-03-25 17:38 ` Eli Zaretskii
2006-03-25 18:07 ` Dieter Deyke
2006-03-25 19:58 ` Jason Rumney
2006-03-25 20:39 ` Andreas Schwab
2006-03-25 22:06 ` Eli Zaretskii
2006-03-25 22:38 ` Dieter Deyke
2006-03-26 16:52 ` Dieter Deyke
2006-03-26 20:14 ` Eli Zaretskii
2006-03-18 17:02 ` Zhang Wei
2006-03-18 18:01 ` Eli Zaretskii
2006-03-20 22:41 ` Jason Rumney
2006-03-27 19:43 ` Eli Zaretskii
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=ud5gj5xzc.fsf@comcast.net \
--to=deyke@comcast.net \
--cc=emacs-devel@gnu.org \
--cc=emacs-pretest-bug@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).