Le mercredi 17 mai 2023 à 20:02 +, Gwyn Ciesla via bug-lilypond a écrit :
> Attaching reproducer.
>
> From Fedora bug:
>
> When I attempt to build a score using a PianoStaff or GrandStaff (which
> contains more than one sub-staff), lilypond crashes.
>
> Reproducible: Always
>
> Steps to
Attaching reproducer.
>From Fedora bug:
When I attempt to build a score using a PianoStaff or GrandStaff (which
contains more than one sub-staff), lilypond crashes.
Reproducible: Always
Steps to Reproduce:
1. Attempt to build a minimal reproducer (which I will attach) with
lilypond-2.25.4
Happens to me on Ubuntu as well:
&&
colin@Calvin:/Work$ lilypond Non-Musical.ly
GNU LilyPond 2.25.5 (running Guile 2.2)
Fontconfig error: No writable cache directories
Processing `Non-Musical.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...
Le mercredi 17 mai 2023 à 17:48 -0600, Colin Campbell a écrit :
> Happens to me on Ubuntu as well:
I don't think that's the same bug. Regarding this:
> Fontconfig error: No writable cache directories
This error popped up at some point during the current cycle before being fixed
shortly
Attached console output. I'll do a git pull and recompile a bit later,
and report what happens. Note that the same test file when compiled
using Frescobaldi as a front end, produces the following output:
Starting lilypond 2.25.5 [Non-Musical.ly]...
programming error: unknown context mod tag
On 2023-05-17 18:25, Jean Abou Samra wrote:
Could you please run with `lilypond --verbose` and send the output?
Thanks,
Jean
Now lilypond blows up in make:
colin@Calvin:/Work/lilypond/lilypond/build$ make -j3 SILENT=1
PythonUI_Init()
PythonUI_Init()
PythonUI_Init()