Andreas Rittershofer <[EMAIL PROTECTED]> writes: > Package: guile-1.8 > Version: 1.8.3+1-1 > Severity: normal > > > Starting lilypond ends in: > > lilypond: Symbol `scm_i_freelist' has different size in shared > object, consider re-linking GNU LilyPond 2.10.29 > Speicherzugriffsfehler > > > So lilypond is completely unusable at the moment.
I think this is probably because I uploaded a new guile that re-disabled threads. This was required in order to maintain compatibility with the guile-1.8 that shipped in Etch (upstream didn't maintain ABI compatibility between the threaded and unthreaded version). I suspect this will be fixed with the next lilypond upload, but as a more immediate workaround, if you're comfortable with it, you should be able to just build a local version of the package against the current guile-1.8-dev. Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
