> No need to wait: as I said, I already pushed the fix myself. Next time, > it would be nice if you provided a patch by calling "git format-patch". > That way, we get your commit message as well and the patch is pretty > sure to apply (using "git am" instead of "git apply") and you have less > trouble when rebasing your own branch on master since Git then > recognizes that the commit/patch is already there.
Thank you. Next time, I'll try it. > Huh. I had the impression OpenDarwin is dead anyway. If we have an > actively maintained and free Darwin version, it would of course be nice > if we could support it with an installer from us, but only if we > actually expect people to use our installer. I think that probably few > people use our GNU/Linux installer, and it is not clear whether anybody > actually uses our FreeBSD installer (rather than compile himself or use > the version of LilyPond packaged by FreeBSD). > > But I think PureDarwin/OpenDarwin are a problem for later: I don't think > we supported them in 2.19.15, so it would be important to get 2.19.16 > out first with the currently supported platforms before trying something > new. I don't want PureDarwin / OpenDarwin corresponding lilypond. I want to test the Mac version lilypond. I didn't have Mac. On the other hand, Darwin is the core components and subset of Mac OS X. Therefore, I thought that it could be used as Max OS X substitutes. However, lilypond requires Carbon that are not included in Darwin. It is included only Mac OS X. I found that Darwin could not be used as Mac OS X substitutes. So, I've been prepared Mac. And, I've tested darwin-x86::lilypond that I've build by gcc-4.9.2. In the results, the following command is succeed: $ ./lilypond Correct messages is shown. However, the following command is failed: $ ./lilypond test.ly I've found some issues. Now, I'm trying to fix them. _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
