Bertalan Fodor writes:
> Python 2.3.4
> XXXX
> {/netrel/build/lilypond-2.4.0/share/lilypond,{/netrel/build/lilypond-2.4.0/share
> /lilypond,{/usr/share/lilypond/2.2.5,/usr/share/texmf}}}
> XXXX
Ok, you found a bug. Can you try the patch below? You'll have to at
least rm -rf /netrel/build/lilypond-2.4.0/share .
> And it builds the files.
(Yes, using the installed lilypond-book, my bad..)
Jan.
--- GNUmakefile.in 19 jul 2004 00:40:27 +0200 1.126
+++ GNUmakefile.in 03 nov 2004 10:00:10 +0100
@@ -114,7 +114,8 @@ $(builddir)/share/lilypond-force:
ln -s $(abs-srcdir)/scm
cd $(builddir)/share/lilypond/tex && \
ln -s $(abs-srcdir)/tex source && \
- ln -s ../../../mf/$(outconfbase) generate
+ ln -s ../../../tex/$(outconfbase) tex-out && \
+ ln -s ../../../mf/$(outconfbase) mf-out
cd $(builddir)/share/lilypond/fonts && \
ln -s $(abs-srcdir)/mf source && \
ln -s ../../../mf/$(outconfbase) afm && \
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
_______________________________________________
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
