If I haven't done mistake somewhere,
/home/abuild/rpmbuild/BUILD/lilypond-2.17.18/scripts/build/out/run-and-check
"/usr/bin/lilypond -dpreview -dresolution=150 -o ./out-www
orchestra.ly" "orchestra.preview.log"
succedes while
/home/abuild/rpmbuild/BUILD/lilypond-2.17.19/scripts/build/out/run-and
- Original Message -
From: "Petr Gajdos"
To:
Sent: Friday, August 09, 2013 11:07 AM
Subject: Re: wrt 'Make doc crashing on my PC'
that reason at least on my machine. It seems to me therefore that 2.17.18
do not expose the issue but 2.17.19 does.
That stacks up well with my earlier
"Phil Holmes" writes:
> - Original Message -
> From: "Petr Gajdos"
> To:
> Sent: Friday, August 09, 2013 11:07 AM
> Subject: Re: wrt 'Make doc crashing on my PC'
>
>> that reason at least on my machine. It seems to me therefore that 2.17.18
>> do not expose the issue but 2.17.19 does.
2013/8/3 James
> Well when I run configure in an out of tree build I get the line
>
> --snip--
> checking New Century Schoolbook PFB files...
> /usr/share/fonts/type1/gsfonts/c059013l.pfb
> /usr/share/fonts/type1/gsfonts/c059033l.pfb
> /usr/share/fonts/type1/gsfonts/c059036l.pfb
> /usr/share/font
Is http://code.google.com/p/lilypond/issues/detail?id=2742 of relevance?
--
Phil Holmes
- Original Message -
From: Federico Bruni
To: David Kastrup
Cc: lilypond-devel
Sent: Sunday, August 04, 2013 1:42 AM
Subject: Re: ERROR: Please install required programs: International
2013/8/9 Phil Holmes
> Is http://code.google.com/p/lilypond/issues/detail?id=2742 of relevance?
>
maybe...
but I have texlive-lang-cyrillic installed
this is the relevant part of the configure error:
checking New Century Schoolbook PFB files... configure: WARNING:
/usr/share/texlive/texmf-dist
Federico Bruni writes:
> 2013/8/9 Phil Holmes
>
>> Is http://code.google.com/p/lilypond/issues/detail?id=2742 of relevance?
>>
>
> maybe...
> but I have texlive-lang-cyrillic installed
>
> this is the relevant part of the configure error:
>
> checking New Century Schoolbook PFB files... configur
Phil Holmes philholmes.net> writes:
> - Original Message -
> > that reason at least on my machine. It seems to me therefore that
2.17.18
> > do not expose the issue but 2.17.19 does.
>
> That stacks up well with my earlier investigations. Git besect
identified
> 35d5f2e2ff40e0bd35cf
Hello,
On 10 August 2013 01:07, Keith OHara wrote:
> Phil Holmes philholmes.net> writes:
>
> > - Original Message -
> > > that reason at least on my machine. It seems to me therefore that
> 2.17.18
> > > do not expose the issue but 2.17.19 does.
> >
> > That stacks up well with my earl
