Oops. Sorry about that; thanks for the quick fix, Jan.
-Dave Jedlinsky
From: David Bobroff <[EMAIL PROTECTED]>
Date: Wed, 30 Mar 2005 07:03:06 +
The subject line says it all. 'make all' output this before giving up:
-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include-
I/usr/include
.3355 ChangeLog
--- ChangeLog 29 Mar 2005 18:55:53 - 1.3355
+++ ChangeLog 29 Mar 2005 21:25:56 -
@@ -1,3 +1,9 @@
+2005-03-29 David Jedlinsky <[EMAIL PROTECTED]>
+
+ * configure.in: Detect libutf8/wchar.h variant.
+
+ * stepmake/aclocal.m4: Modify shared size test.
+
In the current CVS (ChangeLog 1.3316), lyrics are typeset with the
Aybabtu-Regular font. If I use the tex backend, the correct ecr fonts
are used.
Did I somehow configure things wrong? Is there documentation for how
the non-tex backend is supposed to work?
Thanks.
-Dave Jedlinsky
__
Building the current cvs (ChangeLog 1.3316), the tex backend has a
slight issue:
$ lilypond -b tex test
GNU LilyPond 2.5.16
Processing `test.ly'
Parsing...
Interpreting music... [5]
Preprocessing graphical objects...
Calculating line breaks... [3][5]
Calculating page breaks...programming error:
Thanks for the hints, Mats. I am indeed using teTeX 3.0, and didn't
apply the GNUmakefile patch mentioned a while back. So the
ec-mftrace.map was incorrect (incidentally, "kpsewhich ecb12.pfa"
still works in this situation). Once I fixed that, the fonts were no
longer jaggy.
I now have lilypon
Apparently, I'm not quite there yet. Using lilypond 2.4.5 works, but
the output text is jagged bitmaps, not smooth Postscript fonts. The
feta fonts are fine; it's just lyrics that are jagged.
Using the various tricks (dvips -Ppdf -u+lilypond.map
-u+ec-mftrace.map) don't change the output, excep
I am running OpenBSD 3.3, which is too out of date for the development
efforts of Matt Jibson and Matthias Kilian. Therefore, I decided to
take on the task of updating all the required packages on my system,
and build lilypond myself.
Using gcc 3.4.3, and fairly recent versions of every required
