[geos-devel] GEOS 3.0.2 fails to compile under MingW Win32

[Obe, Regina]

Mark et. al,

Not sure it matters - hmm I forget which file it was. I probably should
have taken notes, but the  include listings were in a different order
from the trunk.  I added the missing one I think cstring or was it
version, but was hesitant to change the order of the includes to match
trunk since I wasn't sure the significance of the order.

It didn't seem to affect the compilation process as far as I could tell.


Thanks,
Regina

-----Original Message-----
From: geos-devel-bounces at lists.osgeo.org
[mailto:geos-devel-bounces at lists.osgeo.org] On Behalf Of Sean Gillies
Sent: Monday, October 20, 2008 9:42 AM
To: GEOS Development List
Subject: Re: [geos-devel] GEOS 3.0.2 fails to compile under MingW Win32

Mark Cave-Ayland wrote:
> On Sun, 2008-10-19 at 21:48 +0100, Mark Cave-Ayland wrote:
> 
>> My current solution is the attached patch which works by replacing
>> strdup() with a simple malloc() and strcpy() to preserve the old
locale.
>> Note that this will almost certainly need to be applied to the 3.1
>> branch too, although I haven't got as far as trying to compile it on
>> Win32 - yet ;)
> 
> And as if by magic:
> http://trac.osgeo.org/geos/ticket/212
> 
> Cool. In that case, please can this be backported to the 3.0 branch?
And
> I think we also need to backport the gcc-4.3 fixes since Debian and
SUSE
> are now using gcc-4.3 by default (see
>
http://postgis.refractions.net/pipermail/postgis-devel/2008-October/0039
39.html for the SUSE confirmation, and my local machine as of 2 hours
ago is the Debian Lenny confirmation).
> 
> 
> ATB,
> 
> Mark.

Mark,

Sorry about not seeing the problem on windows until now. I've backported
and am testing locally (linux) and am game to commit the fix of #212 to
the 3.0 branch. What do you think, Mateusz?

Sean

_______________________________________________
geos-devel mailing list
geos-devel at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/geos-devel
-----------------------------------------
The substance of this message, including any attachments, may be
confidential, legally privileged and/or exempt from disclosure
pursuant to Massachusetts law. It is intended
solely for the addressee. If you received this in error, please
contact the sender and delete the material from any computer.