On Wed 18 Jul 2012 15:44, Graham Percival <gra...@percival-music.ca> writes:
> On Wed, Jul 18, 2012 at 02:39:59PM +0100, Ian Hulin wrote: >> P.S. to Graham/bug-squad: how do we handle this sort of issue for >> LilyPond, if it looks like it's an interoperability problem between >> different GNU projects? > > Presumably there's two different guile versions (we'd be using > either 1.6.x or 1.8.y, presumably gnucash is using 2.z?) both > called libguile-17.dll. I'm not sure how the DLLs get named, but the intention was certainly to give 2.0 a different name (not just soname or version) -- it's libguile-2.0.so on GNU systems. It's possible for the binary names (of the Guile executable itself, not the library) to conflict. In that case I would suffix the different builds. For example, pass --program-suffix=-2.0 to Guile's configure. That way the "guile" binary gets installed as "guile-2.0". Cheers, Andy -- http://wingolog.org/
