Okay I visually inspected one of the buffer differences between 3.1.0 and 3.1.1 and it appears to be a bug fix. In the 3.1.0 the buffer is clearly wrong as it is missing one of the polygons that should have been formed from the original goemetry. In the 3.1.1 it includes the missing polygon.
So its just seems to be the make check that is problematic as far as I can tell. -----Original Message----- From: geos-devel-boun...@lists.osgeo.org [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of Obe, Regina Sent: Friday, June 12, 2009 8:54 AM To: GEOS Development List Subject: RE: [geos-devel] 3.1.1rc1 and 3.0.4rc1 Thought geos 3.1.1rc1 tests fail. Comparing behavior of geos 3.1.1rc1 against geos 3.1.0 stable under PostGIS 1.4SVN under PostgreSQL 8.4 beta 2 with PostGIS torture test, they behave more or less the same. Except in 2 cases the buffer answers are different. I assume that is to be expected since a lot of work went into buffer. I haven't checked to see what these buffer differences are though. But they are buffers dealing with geometry collection and multilinestring. -----Original Message----- From: geos-devel-boun...@lists.osgeo.org [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of Obe, Regina Sent: Friday, June 12, 2009 8:00 AM To: GEOS Development List Cc: Mark Cave-Ayland Subject: RE: [geos-devel] 3.1.1rc1 and 3.0.4rc1 So in conclusion make check on MingW -- 3.1.1rc1 -- barely gets in the door (I think it passed one test before vomitting) 3.0.4rc1 make check -- chugs along for a while ang then geos_unit.exe crashes with message creating geos_unit.exe .libs/lt-geos_unit.exe.c: In function `main': .libs/lt-geos_unit.exe.c:79: warning: passing arg 2 of `execv' from incompatible pointer type ----------------------------------------- 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. _______________________________________________ geos-devel mailing list geos-devel@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/geos-devel _______________________________________________ geos-devel mailing list geos-devel@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/geos-devel _______________________________________________ geos-devel mailing list geos-devel@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/geos-devel