On Tue, 2016-01-12 at 11:45 -0600, Jeremiah Benham wrote: > 2.18.2 was the version that crashed. It was 2.19 that worked.
We've had a misunderstanding here. This is the quote from my reply to Ellen Schwindt who was the second person to report a LilyPond crash: 8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8>< > > This is the second report like this: I tried it just now and my > version > > of LilyPond typeset it without problem. Then I tested it on a > Windows > > box and, sure enough, LilyPond threw up a window (well, to be > precise it > > is something called the mingw runtime that throws up the window). > > > > The first good news is that if I choose "Ignore" it did go on to > > generate a typeset score. > > > > But the proper fix is to get the stable version of LilyPond (Denemo > for > > windows is shipped with an experimental version, for obscure > reasons). > > This is not too horrendous. I just tried it out. You go to > lilypond.org > > and to Download Stable and choose windows version. Once downloaded > you > > install it taking the defaults (so it installs in C:\Program Files > > \LilyPond) and then - this is the tricky bit - you go to > Edit->Change > > Preferences->Externals > > and in the LilyPond field you change > > 8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8>< As it says there, I diagnosed this as a failure of the 2.19.x that we shipped with Denemo and advised getting 2.18.2 Is there a still earlier email where lilypond crashes were being reported for 2.18.x ? My memory and my search techniques are not good enough to answer that. Let's try straight LilyPond stable and work from there. > The problem was that you told me their was a big with this version > and that we need to revert to stable version. I'm a bit puzzled by that sentence - that is what I recall, a bug showed up with the 2.19 and we needed to revert to stable. > > Now do you want to keep building with 2.18 2 or should we use > unstable. Maybe they can patch what ever bug that we find. The big may > be even fixed by now. It was an older unstable snapshot. let's try stable. If there's a bug that shows in 2.18.2 as delivered from LilyPond.org, LilyPond gang will fix it otherwise we will have to figure out what is wrong with our build. Richard _______________________________________________ Denemo-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/denemo-devel
