From: Tak Ota <Takaaki.Ota@am.sony.com>
Cc: lektu@terra.es, emacs-devel@gnu.org, andrewi@gnu.org
Subject: Re: lost argument and doc string
Date: Mon, 11 Feb 2002 18:32:54 -0800 (PST) [thread overview]
Message-ID: <20020211.183254.01366081.Takaaki.Ota@am.sony.com> (raw)
In-Reply-To: <4634-Mon11Feb2002213740+0200-eliz@is.elta.co.il>
Mon, 11 Feb 2002 21:37:40 +0200: "Eli Zaretskii" <eliz@is.elta.co.il> wrote:
> > From: Juanma Barranquero <lektu@terra.es>
> > Date: Mon, 11 Feb 2002 17:34:14 +0100
> >
> > > Is it possible that the change in the way doc strings are put in C files
> > > confuses the Windows port, either the make-docfile program or Emacs
> > > itself?
> >
> > Maybe, but then why some docstrings can be seen just fine?
>
> Because some doc strings come from Lisp files?
>
> But that's a stab in the dark; it would be nice if someone could step
> with a debugger through the offending code and see what's going on
> there.
A debugger was found to be helpless in this particular case. I think
I found the real cause of the problem. The first suspected culprit
make-docfile turned out to be innocent by borrowing the make-docfile
from 21.1.90 produced the same result. The real problem is in
makefile.w32-in. I don't know much about how make-docfile operates
but it obviously expects some .elc files instead of .el files. By
comparing the makefile with the one in 21.1.90 and restoring those elc
definitions in lisp= macro the lost doc strings are recovered.
I suppose the following change in lib-src/ChangeLog is responsible
for this.
-Tak
2001-11-30 Andrew Innes <andrewi@gnu.org>
* makefile.w32-in (FACE_SUPPORT):
(MOUSE_SUPPORT):
(FLOAT_SUPPORT):
(WINNT_SUPPORT):
(lisp): Reference .el files instead of .elc files, to simplify
bootstrapping.
($(DOC)): Change dependency to just `make-docfile'.
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-02-12 2:32 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-10 6:59 lost argument and doc string Tak Ota
2002-02-10 17:08 ` Eli Zaretskii
2002-02-10 17:32 ` Pavel Janík
2002-02-10 23:28 ` Tak Ota
2002-02-11 5:48 ` Pavel Janík
2002-02-11 5:48 ` Eli Zaretskii
2002-02-11 16:34 ` Juanma Barranquero
2002-02-11 19:37 ` Eli Zaretskii
2002-02-12 2:32 ` Tak Ota [this message]
2002-02-12 8:35 ` Eli Zaretskii
2002-02-12 14:23 ` Tak Ota
2002-02-12 18:57 ` Jason Rumney
2002-02-12 19:48 ` Tak Ota
2002-02-13 5:43 ` Eli Zaretskii
2002-02-13 6:01 ` Tak Ota
2002-02-13 13:40 ` Andreas Schwab
2002-02-13 14:23 ` Eli Zaretskii
2002-02-13 19:50 ` Jason Rumney
2002-02-13 20:22 ` Tak Ota
2002-02-13 21:02 ` Jason Rumney
2002-02-14 7:36 ` Tak Ota
2002-02-15 10:36 ` Richard Stallman
2002-02-15 20:36 ` Tak Ota
2002-02-13 21:00 ` Tak Ota
2002-02-14 3:11 ` Richard Stallman
2002-02-14 15:13 ` Tak Ota
2002-02-13 15:37 ` Richard Stallman
2002-02-11 18:48 ` Richard Stallman
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=20020211.183254.01366081.Takaaki.Ota@am.sony.com \
--to=takaaki.ota@am.sony.com \
--cc=andrewi@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lektu@terra.es \
/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).