Am Mo., 7. Jan. 2019 um 08:10 Uhr schrieb Werner LEMBERG <w...@gnu.org>: > > > Folks, > > > using gub pull requests > > https://github.com/gperciva/gub/pull/53 > https://github.com/gperciva/gub/pull/54 > > together with > > https://sourceforge.net/p/testlilyissues/issues/5456/ > > allows me to successfully run gub's `make lilypond' on my machine, > including regression tests and documentation! This means that > a lilypond build is no longer bound to a certain architecture, user, > or top-level directory. As soon as issue #5456 is in git master you > can test this :-) > > > Werner > > > PS: If you want to test this immediately, do the following. > > . Apply the patches from the above two pull requests to gub's git > repository. > . Apply https://codereview.appspot.com/349090043 to lilypond's git. > . Move the modified file `output-distance.py' to from lilypond's git > to $HOME. > . Do `git reset --hard' in lilypond's git. > . Apply the attached patch to gub's `lilypond.make':
Hi Werner, because you wrote "no longer bound to a certain architecture", I gave it a try on my 64-bit Ubuntu 18.04. Following the above described steps (and skipping 'make bootsrap') 'make lilypond' fails with [...] building package: darwin-ppc::odcctools *** Stage: download (odcctools, darwin-ppc) *** Stage: untar (odcctools, darwin-ppc) *** Stage: patch (odcctools, darwin-ppc) sh: 1: ./32bit: not found error: cannot run 32 bit executable: 32bit [...] Not really surprising for me, or should it been working? I'll redo testings with a 32-bit OS soon. Thanks for all your hard work on it!! Cheers, Harm _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
