This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
RE: PING Jan Nieuwenhuizen re libguile17
- From: Jan Nieuwenhuizen <janneke-list at xs4all dot nl>
- To: Dave Korn <dave dot korn at artimi dot com>
- Cc: cygwin-apps at cygwin dot com, hanwen <hanwen at xs4all dot nl>
- Date: Mon, 04 Feb 2008 15:09:39 +0100
- Subject: RE: PING Jan Nieuwenhuizen re libguile17
- References: <008701c860e3$466e8530$2e08a8c0@CAM.ARTIMI.COM> <1201795510.29879.13.camel@peder.flower> <012101c86429$d1714fc0$2e08a8c0@CAM.ARTIMI.COM>
Dave Korn writes:
Hi Dave,
> 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
I see...
> 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.
LilyPond does not support gcc 3.x anymore, would it be of any use to
try rebuilding guile with the --enable-fully-dynamic string option?
Jan.
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org