From: Michael Cook <michael@waxrat.com>
To: ding@gnus.org
Subject: Node `...' previously defined at line 29776.
Date: Tue, 01 May 2007 21:00:11 -0400 [thread overview]
Message-ID: <m3wszs9h0k.fsf@pigpen.waxrat.com> (raw)
FYI, I just updated from the CVS repository and got the following
build error:
gmake[2]: Leaving directory `/local/gnus/repo/gnus/lisp'
cd texi && gmake EMACS="emacs" install
gmake[2]: Entering directory `/local/gnus/repo/gnus/texi'
if test "xmakeinfo" != "xno" ; then \
LC_ALL=C makeinfo -I . --enable-encoding -o gnus gnus.texi; \
else \
rm -f gnus; \
emacs -batch -q -no-site-file -l ./infohack.el -f batch-makeinfo gnus.texi; \
fi
/local/gnus/repo/gnus/texi//doclicense.texi:2: Node `GNU Free Documentation License' previously defined at line 29776.
makeinfo: Removing output file `gnus' due to errors; use --force to preserve.
gmake[2]: *** [gnus] Error 1
gmake[2]: Leaving directory `/local/gnus/repo/gnus/texi'
gmake[1]: *** [install] Error 2
gmake[1]: Leaving directory `/local/gnus/repo/gnus'
gmake: *** [install] Error 2
gmake: Leaving directory `/local/gnus/repo'
Michael
next reply other threads:[~2007-05-02 1:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 1:00 Michael Cook [this message]
2007-05-02 1:26 ` Katsumi Yamaoka
2007-05-02 21:18 ` Reiner Steib
2007-05-03 2:47 ` Miles Bader
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=m3wszs9h0k.fsf@pigpen.waxrat.com \
--to=michael@waxrat.com \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).