This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
RE: PING Jan Nieuwenhuizen re libguile17
- From: "Dave Korn" <dave dot korn at artimi dot com>
- To: "'Jan Nieuwenhuizen'" <janneke-list at xs4all dot nl>
- Cc: <cygwin-apps at cygwin dot com>, "'hanwen'" <hanwen at xs4all dot nl>
- Date: Mon, 4 Feb 2008 14:54:33 -0000
- 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> <1202134179.2951.44.camel@peder.flower>
On 04 February 2008 14:10, Jan Nieuwenhuizen wrote:
>> 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?
You need to build the /compiler/ using that option, not the target
application, but apart from that yes: it should then fix your builds of
lilypond, libguile, et al.
cheers,
DaveK
--
Can't think of a witty .sigline today....