Thomas Morley <thomasmorle...@gmail.com> writes: > Hi all, > > guile-2.2 is released. So I plan to implement most patches from the > remotes/origin/dev/guile-v2-work-branch and those I've put locally on > top of it. > > This will sometimes require some updating of those patches. Most of > them were created to make lily work with guile-2.0.x. Also, I'd like > to check whether those patches are still all needed: guile-devs > claimed a far better port-encoding-handling wrt to utf-8, etc. We will > see... > > The main question: > I'd like to facilitate review by putting them on one by one. > Though this may result in commits with only partly working LilyPond, > if compiled with guile-2.2
Well, that's not exactly a regression. > For example the attached. > It makes configure find all the needed files when done with --enable-guile2 > But make will fail. > (lily with guile-1.8 should be unaffected.) The problem is more that Guile-2.0 will not work at all any more, and it will take some time until Guile-2.2 becomes generally available. Now it's not like compilation with Guile-2.0 is doing us a lot of favors anyway. -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
