Am Di., 11. Juni 2019 um 21:27 Uhr schrieb David Kastrup <d...@gnu.org>: > > Thomas Morley <thomasmorle...@gmail.com> writes: > > > Am Di., 11. Juni 2019 um 18:35 Uhr schrieb Thomas Morley > > <thomasmorle...@gmail.com>: > >> > >> Am Di., 11. Juni 2019 um 17:57 Uhr schrieb Thomas Morley > >> <thomasmorle...@gmail.com>: > >> > >> > Just for fun I then tried to go for > >> > https://github.com/lilypond/lilypond > >> > a repository once set up by Janek. > >> > ~/gub (master)$ make > >> > LILYPOND_REPO_URL=https://github.com/lilypond/lilypond.git lilypond > >> > => > >> [...] > >> > make: *** [lilypond] Error 2 > >> > >> Probably I should have done: > >> LILYPOND_REPO_URL=git://github.com/lilypond/lilypond.git > >> Note the git:// instead of https:// > >> At least it errors not immediately. I'll report later. > > > > Build failed because of > > https://sourceforge.net/p/testlilyissues/issues/5526/ > > which is fixed in master of our official repo. > > Unlikely. A missing \version statement in a file that isn't even > present in the branch cannot do much harm. Or are we not talking about > the stable/2.20 branch? > > -- > David Kastrup
I tried to build from _master_, so the file swing.ly is present, fixed in the official repo, not fixed in Janek's repo. Anyway, I'll think building from a local repo will not work (at least someone can come up with a fix for the problem mentioned in my other mail). I regard it not unlikely the build from Janek's repo would have succeeded, _if_ said fix would have been present. Thus, I'll go for an own repo as soon as I can spare some time. Probably next weekend ... Cheers, Harm _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
