From: "Stefan Monnier" <monnier+gnu/emacs@RUM.cs.yale.edu>
Cc: Juanma Barranquero <lektu@terra.es>,
"Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>,
emacs-devel@gnu.org
Subject: Re: No doc strings from DOC
Date: Thu, 04 Apr 2002 13:13:36 -0500 [thread overview]
Message-ID: <200204041813.g34IDab18347@rum.cs.yale.edu> (raw)
In-Reply-To: m3it7772uw.fsf@nyaumo.btinternet.com
> Juanma Barranquero <lektu@terra.es> writes:
>
> > On Thu, 04 Apr 2002 10:27:08 +0200, Juanma Barranquero <lektu@terra.es> wrote:
> >
> > > Any more hints on how to debug this?
> >
> > Hmmmm...
> >
> > After:
> >
> > nmake realclean
> > nmake bootstrap
> > nmake install
> >
> > some functions from preloaded files do not have docstrings (their
> > bytecode function object has 0 on the DOCSTRING element).
>
> I remember a few weeks ago we reverted a change to build the DOC
> file from the .el files on Windows, since building with the .el files
> does not work. I think there may have been another part of that
> change that we forgot to revert, ie regenerating the DOC file after
> the .elc files have been compiled (perhaps in a different makefile
> than the other change).
The DOC file is not necessary for the bootstrap, so it would
be simpler to not generate it before having generated the elc files.
Stefan
next prev parent reply other threads:[~2002-04-04 18:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-03 11:10 No doc strings from DOC Juanma Barranquero
2002-04-03 15:45 ` Juanma Barranquero
2002-04-03 19:14 ` Stefan Monnier
2002-04-03 16:18 ` Stefan Monnier
2002-04-03 16:58 ` Juanma Barranquero
2002-04-03 17:04 ` Stefan Monnier
2002-04-03 17:11 ` Juanma Barranquero
2002-04-03 17:32 ` Stefan Monnier
2002-04-04 8:27 ` Juanma Barranquero
2002-04-04 14:51 ` Juanma Barranquero
2002-04-04 18:09 ` Jason Rumney
2002-04-04 18:13 ` Stefan Monnier [this message]
2002-04-10 11:21 ` Juanma Barranquero
2002-04-10 16:36 ` Stefan Monnier
2002-04-10 20:19 ` Jason Rumney
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=200204041813.g34IDab18347@rum.cs.yale.edu \
--to=monnier+gnu/emacs@rum.cs.yale.edu \
--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 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.