|
From: | Knut Petersen |
Subject: | Re: guile-2.0 and debian |
Date: | Sat, 26 Nov 2016 00:08:26 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.0 |
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 <address@hidden> 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
[Prev in Thread] | Current Thread | [Next in Thread] |