On 31 January 2008 16:05, Jan Nieuwenhuizen wrote: > Dave Korn: > > Hi Dave, > >> Hi Jan, if you're currently around, > > Thanks for the ping, I've been away.
Thanks for getting back to me! >> It looks to me as if cygguile-17.dll needs to be rebuilt with an >> up-to-date gcc with the fix for throwing strings across dll boundaries. > > Hmm. It seems that gcc is at > > install: release/gcc/gcc-core/gcc-core-3.4.4-3.tar.bz2 3704219 > f50239b82e65821f5 > > I have been using gcc-4.1.1. Have cygwin specific fixes been made? Are > these fixes in upstream gcc 4.x? Do I need a configure flag? Ah, if you used 4.1.1 to compile libguile, that would certainly explain it. There is a cygwin-local fix in 3.4.4-3 that is essential for correctness when throwing exceptions or passing std::string objects across DLL boundaries. This is a bug in upstream gcc: see http://gcc.gnu.org/PR24196 The fix is almost - but not quite - equivalent to applying the "--enable-fully-dynamic-string" configure option, but hopefully has the advantage of being ABI-compatible. As a bit of generic advice (to all package maintainers, not just you), I really wouldn't recommend using 4.x as a production compiler for cygwin packages for distribution just yet. cheers, DaveK -- Can't think of a witty .sigline today....