Re: misdetection of mftrace in 2.10.1

Am Freitag, den 08.12.2006, 18:51 +0100 schrieb Thomas Frank: Same problem here with guile-config = 1.6.7, which is exactly the installed version. Any work-around? Thanks to Daniels hint I constructed a patch, that essentially reverts the relevant changes in configure to the 2.10.0 state. I

misdetection of mftrace in 2.10.1

Hi List, I downloaded the 2.10.1 tarball of lilypond but configure claims that I only have mftrace 1.1 installed, while 1.1.19 is needed. However I do have version 1.1.19 and only that version of mftrace installed. As far as I understand stepmake uses mftrace --version to learn about the

Re: Compiling Lilypond 1.7.4

Ralph Little wrote: Hi, I am trying to get Lily 1.7.4 up and running on Redhat 8 I have built and installed Guile1.6 from source, and there is a /usr/local/lib/libguile.so.12 (sym linked to libguile.so.12.3.0), and guile (/usr/local/bin/guile) fires up fine. I saw some posts on a similar vein

Re: common rests between two voices in one staff

Hi, first of all thanks for the quick answers! However after reading the fine manual I found a far simpler solution to the problem which might be interesting to those who helped me(and others) as well: simply set the #'maximum-rest-count property of the staff. e.g.(typical SATB piece without

common rests between two voices in one staff

I am just doing some SATB pieces and I wonder if there is a way to share common rests between the two voices of one staff. The default behaviour for something like the following is that there are two rests generated, one typeset above the other. I know of the possibility to use s instead of r in