> I've been struggling today to 'make check' as part of the normal set > of commands I use to patch test. > > I've gone back, one by one, and this is the commit that 'breaks' my > patch testing > > Issue 5450: relocate.cc: Introduce new command `set?' > commit 8067320145662554d85e59e6b9e6df3770f9e4a3
Actually, I can hardly believe this is the culprit, since the patch adds new functionality that has to be explicitly requested – and within lilypond's make system this doesn't happen. > I don't know what the difference is between the two 'make' functions > but at the moment I cannot do a full set of tests on patches. Whatever :-) I found a problem with `output-distance.py', which I hot-fixed in staging. Please retry! Werner _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel