Hello All,
The following exit code pops up
Exited with return code -1073741819.
It seems to be related to using a slur, (..), on three chords.
Any ideas?
Thank you.
Mark
2018-09-05 13:22 GMT+02:00 David Kastrup :
> The \tempo does
> not actually appear, though.
Indeed.
> So which architecture and GCC version are we talking about in your case?
$ uname -a
Linux dmif-lm2 4.17.18-200.fc28.x86_64 #1 SMP Wed Aug 22 19:08:07 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
$ gc
Davide Liessi writes:
> Hi all.
> Compiling this file:
>
> \version "2.19.82"
> {
> c1
> \tempo "a"
> %c1
> }
>
> with the system-provided LilyPond 2.19.82 on Fedora 28 I get this error:
>
> lilypond 2.19.82 [Senza nome] in avvio...
> Elaborazione di «/tmp/frescobaldi-nw1vbdie/tmpe_aojklz/d
Hi all.
Compiling this file:
\version "2.19.82"
{
c1
\tempo "a"
%c1
}
with the system-provided LilyPond 2.19.82 on Fedora 28 I get this error:
lilypond 2.19.82 [Senza nome] in avvio...
Elaborazione di «/tmp/frescobaldi-nw1vbdie/tmpe_aojklz/document.ly»
Analisi...
Interpretazione della musi
Am 11.11.2015 um 22:16 schrieb tisimst:
> The \version statement mostly serves two purposes:
>
> 1. Remind you what compiler version you initially coded it for
> 2. Makes it possible for convert-ly to upgrade it to newer versions when
> desired
However (and including Simon's comments) I've always
Johannes,
On Wed, Nov 11, 2015 at 1:54 PM, Johannes Waldmann [via Lilypond] <
ml-node+s1069038n183442...@n5.nabble.com> wrote:
> Hi,
>
> it's really not a big deal since I have a work-around
> (ignore the exit code in my Makefile)
>
> I understand that specifying a
Hi,
it's really not a big deal since I have a work-around
(ignore the exit code in my Makefile)
I understand that specifying and checking the version
can be useful. I am just saying that the actual message
and behaviour (exit code) is surprising.
>From the compilers I know (say, gcc)
t
Am 11.11.2015 um 14:19 schrieb Johannes Waldmann:
Hi. I am getting this:
Parsing...
error: program too old: 2.18.2 (file requires: 2.19.0)
but apparently it's not an error,
Yes, it is because the file states to need version 2.19.0 and you cannot
be sure that 2.18.2 will be sufficient.
since
Hi. I am getting this:
Parsing...
error: program too old: 2.18.2 (file requires: 2.19.0)
but apparently it's not an error,
since the processing continues,
and the pdf file is produced.
but still, my Makefile is confused
because the exit code is 1 (not 0)
I can turn off exit code checki
