"Dr. Arne Babenhauserheide" <arne_...@web.de> writes: > Hi Jonas, Hi Mike, > > Jonas Hahnfeld via "Developers list for Guile, the GNU extensibility > library" <guile-devel@gnu.org> writes: > >> The full set of patches can be found here: >> https://gitlab.com/lilypond/lilypond/-/tree/master/release/binaries/patches >> and the build configuration "recipe" is here: >> https://gitlab.com/lilypond/lilypond/-/blob/master/release/binaries/lib/dependencies.py#L642 > … >> first five patches are the most important ones ("learn to walk before >> starting to run"). > > Did you manage to move forward with the patches?
Hello Arne, Things are in progress, but since I've been out of the free software scene for a while, it took me a bit to pull things together: linux box figure out emacs mail again, IMAP, SMTP, debbugs, git am, etc. Patches are tough to get into Guile, so felt I needed to make sure I did everything I could possibly do to use the expected tooling and culture. >From there, I tried to get some of the Guile configurations that I will later reply on for MinGW to first work on Fedora or Ubuntu, which led to work on bugs: 36340: fixes to --disable-networking build 76906: make distcheck doesn't work 76907: potential buffer overflow in getsockopt I stood up a CI/CD to test a variety of OSs and configs over at https://github.com/spk121/guile-portability. That's working well enough to be of use, but, there's more I want to do. Given the way Windows support, or indeed most non-Guix-on-Linux support, has been handled in mainline Guile, I want to be able to provide a complete and exhaustive narrative that answers all possible questions. That CI/CD is running my old Guile patchset. So now I'm actually ready to replace my Guile patchset with mainline Guile and then the Lilypond patches, so I can soon actually answer the original question of if these Lilypond patches are good to go. It has taken me a bit longer than I thought to get all this stood up, because day job is quite busy. Apologies. Regards, Mike Gran
