On 17 Sep 2013, at 12:39 , David Kastrup wrote:
<>
It's not going to make it easier to pinpoint the problem if we only
get
to see it on PPC. As I stated above "this points to a bad compilation
and/or a platform-specific problem. Or something related to garbage
collection."
Agreed, but
Wim van Dommelen writes:
> On 16 Sep 2013, at 21:12 , David Kastrup wrote:
>
>> Not before we get more data. I don't see 0/0 in current master but
>> rather 1/2 as before. So we need to get more data (which platform
>> exactly, which binary etc). Since I can't reproduce this on current
>> mast
On 16 Sep 2013, at 21:12 , David Kastrup wrote:
Not before we get more data. I don't see 0/0 in current master but
rather 1/2 as before. So we need to get more data (which platform
exactly, which binary etc). Since I can't reproduce this on current
master and there has not really been any rel
Correct output with Windows on 2.17.26. Let's stop reporting good output
until the OP tells us where the bad output comes from.
warning: barcheck failed at: 1/2
c'4
d | e f g a b c
--
Phil Holmes
___
lilypond-user mailing list
l
2013/9/16 Wim van Dommelen :
> I downloaded the newest version (2.17.26) today and saw a strange message
> converning barcheck. It lost the
>
> This sample code:
>
> \version "2.17.26"
>
> \relative f {
> c'4 d | e f g a b c
> }
>
> produces this error:
>
> GNU LilyPond 2.17.26
> Processing
Concerning the error message, I too see 1/2 in my log here. If that
helps...no 0/0 here.
David Kastrup wrote
> Wim van Dommelen <
> mail@
> > writes:
>
>> I downloaded the newest version (2.17.26) today and saw a strange
>> message converning barcheck. It lost the
>>
>> This sample code:
>>
>>
Wim van Dommelen writes:
> I downloaded the newest version (2.17.26) today and saw a strange
> message converning barcheck. It lost the
>
> This sample code:
>
> \version "2.17.26"
>
> \relative f {
> c'4 d | e f g a b c
> }
>
> produces this error:
>
> GNU L
Hello,
I don't quite understand. The bar check failed because it's in the wrong
place, isn't it?
Since LilyPond assumes 4/4 time by default (and since you didn't include any
meter manually), the bar should be between the F and G, right? That would be
4/4 time.
LilyPond is expecting 4/4 common t
I downloaded the newest version (2.17.26) today and saw a strange
message converning barcheck. It lost the
This sample code:
\version "2.17.26"
\relative f {
c'4 d | e f g a b c
}
produces this error:
GNU LilyPond 2.17.26
Processing `t
