Hello, I noticed an interesting thread a few days ago on the Guile mailing list related to LilyPond. Here is the thread:
http://lists.gnu.org/archive/html/guile-devel/2008-12/msg00039.html The suggested fix is trivial, and I've tested the latest git with Guile 1.8.6 and 1.8.4 on GNU/Linux x86. I don't know if any other part of the source code should be changed, but I haven't noticed any side-effects yet. Attached is the patch I've been using. Thanks, Patrick
From 96578cc3eef17839bd7d8b404f02ccc72565e652 Mon Sep 17 00:00:00 2001 From: Patrick McCarty <[email protected]> Date: Tue, 23 Dec 2008 22:50:50 -0800 Subject: [PATCH] Fix for Guile 1.8.6 * latest Guile forbids the call to scm_fill_input () Signed-off-by: Patrick McCarty <[email protected]> --- lily/parse-scm.cc | 3 --- 1 files changed, 0 insertions(+), 3 deletions(-) diff --git a/lily/parse-scm.cc b/lily/parse-scm.cc index f55be98..409ba88 100644 --- a/lily/parse-scm.cc +++ b/lily/parse-scm.cc @@ -38,9 +38,6 @@ internal_ly_parse_scm (Parse_start *ps) SCM answer = SCM_UNSPECIFIED; SCM form = scm_read (port); - /* Reset read_buf for scm_ftell. - Shouldn't scm_read () do this for us? */ - scm_fill_input (port); SCM to = scm_ftell (port); ps->nchars = scm_to_int (to) - scm_to_int (from); -- 1.6.1
_______________________________________________ lilypond-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/lilypond-devel
