Hi Antonio!
TBH I didn't try to compile lilypond using guile-1.8 with my patches
applied, I can give it a go in the next days.
I added your patches in numerical order as single commits to my local branch on
top
of current master and started a "git bisect run" process to investigate which
of your
patches breaks building lilypond with guile 1.8 with the following result:
530823b891f732293ab4b6311b0ca96b1e863c88 is the first bad commit
commit 530823b891f732293ab4b6311b0ca96b1e863c88
Author: Antonio Ospite <a...@ao2.it>
Date: Wed Oct 26 16:42:32 2016 +0200
Update changes from commit 122525f (Keep GUILEv2 from redecoding string
input)
Update the changes from commit 122525f (Source_file::init_port: Keep
GUILEv2 from redecoding string input) to follow what was done in commit
652f454 (Add lily/lily-modules.cc).
cu,
Knut
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
