From: Denis Bueno <dbueno@cc.gatech.edu>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Bootstrap shouldn't give up due to missing xrefs in the manual
Date: Tue, 30 Nov 2004 22:18:45 -0500 [thread overview]
Message-ID: <B5F2835E-4347-11D9-886D-000D933925E0@cc.gatech.edu> (raw)
In-Reply-To: <E1CZKgE-0003cI-N1@fencepost.gnu.org>
On 30 Nov 2004, at 21.57, Richard Stallman wrote:
> Does this patch eliminate the problem?
Works for me, on 30 Nov.
uname -a: Darwin johngalt.local 7.6.0 Darwin Kernel Version 7.6.0: Sun
Oct 10 12:05:27 PDT 2004; root:xnu/xnu-517.9.4.obj~1/RELEASE_PPC Power
Macintosh powerpc
>
> *** 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)
>
>
> _______________________________________________
> Emacs-devel mailing list
> Emacs-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-devel
>
>
--
Denis Bueno
PGP: http://pgp.mit.edu:11371/pks/lookup?search=0xA1B51B4B&op=index
"Be careful about reading health books. You may die of a misprint." -
Mark Twain
next prev parent reply other threads:[~2004-12-01 3:18 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 [this message]
2004-12-01 4:33 ` Luc Teirlinck
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=B5F2835E-4347-11D9-886D-000D933925E0@cc.gatech.edu \
--to=dbueno@cc.gatech.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).