From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Bootstrap shouldn't give up due to missing xrefs in the manual
Date: Tue, 30 Nov 2004 22:33:28 -0600 (CST) [thread overview]
Message-ID: <200412010433.iB14XSQ08115@raven.dms.auburn.edu> (raw)
In-Reply-To: <E1CZKgE-0003cI-N1@fencepost.gnu.org> (message from Richard Stallman on Tue, 30 Nov 2004 21:57:22 -0500)
Richard Stallman wrote:
Does this patch eliminate the problem?
*** Makefile.in 11 Nov 2004 09:58:10 -0500 1.298
--- Makefile.in 30 Nov 2004 21:19:32 -0500
***************
*** 719,727 ****
# put the info files in $(srcdir),
# so we can do ok running make in the build dir.
info: force-info
! (cd man; $(MAKE) $(MFLAGS) info)
! (cd lispref; $(MAKE) $(MFLAGS) info)
! (cd lispintro; $(MAKE) $(MFLAGS) info)
dvi:
(cd man; $(MAKE) $(MFLAGS) dvi)
(cd lispref; $(MAKE) $(MFLAGS) elisp.dvi)
--- 719,727 ----
# put the info files in $(srcdir),
# so we can do ok running make in the build dir.
info: force-info
! -(cd man; $(MAKE) $(MFLAGS) info)
! -(cd lispref; $(MAKE) $(MFLAGS) info)
! -(cd lispintro; $(MAKE) $(MFLAGS) info)
dvi:
(cd man; $(MAKE) $(MFLAGS) dvi)
(cd lispref; $(MAKE) $(MFLAGS) elisp.dvi)
For me that gives the same problem with a "missing separator" as your
other patch. Because it apparently worked for somebody else,
something must be going locally wrong. I will try to figure out what.
So the problem with your other patch I replied about previously might
be local too.
I can not check out the effects of the patch above because it somehow
breaks bootstrapping for me. (Again, probably just a local problem.)
But how are people going to notice after your patch that there were
problems building a manual? Hopefully that will still be completely
apparent and impossible to overlook and hopefully people will still
point it out to emacs-pretest-bug or emacs-devel. Otherwise, this
could, in my opinion, be a step backward.
Sincerely,
Luc.
prev parent reply other threads:[~2004-12-01 4:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-01 2:57 Bootstrap shouldn't give up due to missing xrefs in the manual Richard Stallman
2004-12-01 3:18 ` Denis Bueno
2004-12-01 4:33 ` Luc Teirlinck [this message]
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=200412010433.iB14XSQ08115@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--cc=emacs-devel@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).