all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-pretest-bug@gnu.org, emacs-devel@gnu.org
Subject: Re: old bootstrap error emerges again
Date: Sun, 19 Mar 2006 00:55:23 +0200	[thread overview]
Message-ID: <u1wwzxt0k.fsf@gnu.org> (raw)
In-Reply-To: <ud5gj5xzc.fsf@comcast.net> (message from Dieter Deyke on Sat, 18 Mar 2006 12:55:35 -0700)

> From: Dieter Deyke <deyke@comcast.net>
> Cc: emacs-pretest-bug@gnu.org, emacs-devel@gnu.org
> Date: Sat, 18 Mar 2006 12:55:35 -0700
> 
> I'm not sure on how to debug this. Let me start to point out that
> there were 3 errors about missing DOC

Yes, I've seen those as well in your transcript.  Needless to say, in
my builds none of them are present.

> but the first 2 were not fatal:

No, they are all fatal.  It's just that the shell's for loop invoked
by Make doesn't stop until it finishes (you will see that
url/vc-dav.el is the last Lisp file that is compiled), so Make only
sees the non-zero exit status when the list of files to compile is
exhausted and the subsidiary shell exits.

> 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.

In my builds, I don't have DOC-X either, at this stage of the build.
But the problems still don't happen for me.  I think Emacs shouldn't
look for the doc string file at all at this place.  The DOC vs DOC-X
thing was just another strange thing, so I mentioned it.

> So, could you please guide me in what I have to do to debug this?

Well, one way to try to debug this is to say "make bootstrap" again
(without the workaround), let it fail, then run Emacs under GDB and
let it byte-compile the offending file vc-dav.el with precisely the
same command-line arguments as when Emacs is run from Make.  But
before you run Emacs, after starting GDB, set a breakpoint in doc.c,
in the function get_doc_string, on the line which says:

	error ("Cannot open doc string file \"%s\"", name);

(this is the line that displays the error message and aborts the
compilation).  When this breakpoint breaks, please post here the
backtrace.  Maybe that would give us some ideas.

TIA

  parent reply	other threads:[~2006-03-18 22: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
2006-03-18 21:24             ` Jason Rumney
2006-03-18 21:45               ` Dieter Deyke
2006-03-18 22:55             ` Eli Zaretskii [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=u1wwzxt0k.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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 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.