Marc Hohl <m...@hohlart.de> writes:
> Well, it seems to be not as simple as that.
>
> I did a 'make test' on my patch. This fails, obviously.
> The console says:
>
> Dissecting...
> Writing snippets...
> Processing...
> Processing
> /home/marc/git/lilypond/out/lybook-testdb/snippet-names-3552501373601762147.ly
> Please see
> /home/marc/git/lilypond/out/lybook-testdb/snippet-names-3552501373601762147.log
> Ok. So far, so bad. Now I look at the log file.
>
> marc@olivia ~/git/lilypond (barlineII)$ more
> /home/marc/git/lilypond/out/lybook-testdb/snippet-names-3552501373601762147.log
> GNU LilyPond 2.17.4
> marc@olivia ~/git/lilypond (barlineII)$
That would seem like the bulk of the log went elsewhere.
> Ok, this is what James mentioned for the faulty patchy run.
>
> The file snippet-names-3552501373601762147.ly contains
>
> snippet-map-3552501373601762147.ly
> b4/lily-1ce78b89.ly
> f8/lily-25dab396.ly
> 37/lily-4583781c.ly
> 3d/lily-a69e10a7.ly
> ...
> ...
> ...
> 15/lily-c90f9b1c.ly
>
> Since only the starting message appears, the fault is probably
> at the beginning of the list of files, so I look at
> snippet-map-3552501373601762147.ly
>
> #(define version-seen #t)
> #(define output-empty-score-list #f)
> #(ly:add-file-name-alist '(("59/lily-6e61a987.ly"
> . "out-test/collated-files.tel
> y")
> ...
> ...
> ...
The first file just reestablishes mappings and is not likely supposed to
produce output. I'd take a look at
b4/lily-1ce78b89.ly
and its log file instead.
--
David Kastrup
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
