Well, it just so happened that the first file I tried on Arch makes
lilypond dump core, sheer bad luck. As per the suggestion here (which
I didn't even think of, too busy rushing into worrying about this) my
other files compile fine. So in fact there is no real issue. I'll
binary chop the file to s
Jonas' idea is good. If you (can) share your score with Jonas, don't
hesitate to share with me, and I'd be happy to try and compile it and tell
you if I run in the same problem. With three distros instead of one, we
might be able to narrow down a little the source of the issue.
Claire
On Wed, Jun
Am Mittwoch, den 24.06.2020, 19:17 +1000 schrieb Andrew Bernard:
> Just getting back into lilypond but nowadays on Arch Linux. Sorry to
> say both recent versions dump core:
> ...
> elapsed time: 0.61 seconds
> Element count 12833 (spanners 1146)
> Preprocessing graphical objects...
> Grob count 19
I'm on Manjaro KDE 5.4.44-1, whis is Arch-based. I use lilypond 2.20.0-3
(build date 2020/03/16, packager Antonio Rojas : aro...@archlinux.org) and
it works fine for me. If I'm not mistaken, Manjaro uses Arch repositories,
with some additional code review before incorporating the last changes, so
t
Just getting back into lilypond but nowadays on Arch Linux. Sorry to
say both recent versions dump core:
...
elapsed time: 0.61 seconds
Element count 12833 (spanners 1146)
Preprocessing graphical objects...
Grob count 19105Segmentation fault (core dumped)
Version from Arch AUR repository and Arch
