Re: Backward compatibility status

[Patrick McCarty <pnorcks@gmail.com>]

Hi,

2010/3/6 Ludovic Courtès <ludo@gnu.org>:
>
> A number of Guile-using applications and libraries are tested against
> the latest 1.9 release, using a recent stable release:
>
>  http://hydra.nixos.org/jobset/nixpkgs/guile2test/with-status
>
> As you can see, there’s a lot of red crosses, but you can help!  :-)

Thanks for posting this.

> Here’s a summary of the reasons of these build failures:
>
> | Name                                  | Cause                                           |
> |---------------------------------------+-------------------------------------------------|
> | lilypond-2.13.9                       | `scm_internal_hash_fold' & `scm_t_hash_fold_fn' |

Is this something that should be fixed in LilyPond?

For reference, I'm fairly certain this build failure was introduced
with Guile commit a07010bf1828704edd9a40cadb0eaf820b8f3638.

If I add the typedefs to the appropriate LilyPond header file and use
them, the problem goes away, but I don't know if there are unexpected
side effects of this.  I am unable to test any further, because there
are more build failures down the pipeline.  :-)

Thanks,
Patrick