Lukas-Fabian Moser <l...@gmx.de> writes: > Hi Andrew, > > Am 25.06.19 um 10:56 schrieb Andrew Bernard: >> What is it about 19? Is it some magic borderline number in some unit >> system in lilypond? Do we know? > > I'd rather suspect there's some kind of "anthropic principle" at work > here: The bugs (at least the one I reported) should probably occur for > any staff size in some (staff-size-dependent) situations, but we > notice them with staff sizes that are used in real-world situations, > hence our MWEs expose _those_ cases. But of course I lilypond-user > Mailinglist <lilypond-u...@gnu.org>might be wrong, especially for the > misplaced-note-head problem which occurs for quite a generic > situation. > > Anyway: The misplaced-note-head bug > (https://sourceforge.net/p/testlilyissues/issues/5303/) first appeared > in 2.19.16 (I just found out that it's convenient as well as quite > easy to keep arbitrarily many LilyPond versions installed on the same > account). > > @gcc experts (hence posting to devel also): Unfortunately, I cannot > build 2.19.15 on my machine because of errors of the type: > > /home/lukas/git/lilypond/lily/include/smobs.tcc:98:25: error: invalid > conversion from 'int' to 'scm_unused_struct* (*)(SCM, SCM) {aka > scm_unused_struct* (*)(scm_unused_struct*, scm_unused_struct*)}' > [-fpermissive] > scm_set_smob_equalp (smob_tag_, Super::equal_p); > > I suspect that this is a case of some conversions having become > illegal for later versions of gcc. Is there a cheap way to make the > build succeed in order to be able to bisect for the > misplaced-note-head bug?
I think I used a few cherry-picks commits for building. Embarrassingly, it doesn't appear like I have them in a branch. They were a few C++ commits, a few Texinfo ones, some stuff related to freetype. -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
