Am Donnerstag, 18. Oktober 2007 schrieben Sie:
By "for some time", do you mean "longer than three days" ?
About three days ago, I switched the internals documentation to use
@ruser instead of @usermanref, which is the new macro for that kind of
link. If I did this update correctly -- which I am not claiming -- then
if you rebuild lilypond now, it should create the docs without problems.
Nope, still the same error with current git version.
But your hint about the usermanref => ruser transition was very helpful: It
seems that you missed the file lily/text-interface.cc, which still contained
@usermanref twice. After replacing them with @ruser, everything compiled just
fine. As I don't know anything about the whole docs system of lilypond, I
don't want to commit myself, but rather attach the patch with the fix...
Cheers,
Reinhold
PS: Apparently, the problem did not have anything to do with kubuntu vs.
debian, but rather with the fact that I was working in my own branch on the
kubuntu machine (branched a while ago), while the debian machines were using
origin/master...
------------------------------------------------------------------------
From def93d10a38774b20fa9c320ae0791b22cd6d5f7 Mon Sep 17 00:00:00 2001
From: Lilypond GDP <address@hidden>
Date: Thu, 18 Oct 2007 22:39:28 +0200
Subject: [PATCH] Fix build: usermanref is removed in favor of ruser
---
lily/text-interface.cc | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/lily/text-interface.cc b/lily/text-interface.cc
index de773b6..e8f5aef 100644
--- a/lily/text-interface.cc
+++ b/lily/text-interface.cc
@@ -104,8 +104,8 @@ Text_interface::is_markup_list (SCM x)
ADD_INTERFACE (Text_interface,
- "A scheme markup text, see @usermanref{Text markup} and "
- "@usermanref{New markup command definition}. "
+ "A scheme markup text, see @ruser{Text markup} and "
+ "@ruser{New markup command definition}. "
"\n\n"
"There are two important commands: ly:text-interface::print, which is
a "
"grob callback, and ly:text-interface::interpret-markup ",