<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7653.38">
<TITLE>RE: [geos-devel] RE: [postgis-devel] 1, dot, 3 dot 4!</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<P><FONT SIZE=2>Okay there are apparently are a lot more files to patch.. Mostly one liners, except the CLocalizer seemed to have been reworked and putting in a one line change didn't work, so I copied verbatim from trunk for that one.<BR>
<BR>
I still have more places to patch. And got it to compile up to<BR>
<BR>
DirectedEdge.cpp: In member function std::string geos::planargraph::DirectedEdge::print() const:<BR>
DirectedEdge.cpp:170: error: must #include <typeinfo> before using typeid<BR>
make[3]: *** [DirectedEdge.lo] Error 1<BR>
make[3]: Leaving directory `/projects/geos-3.0.2/source/planargraph'<BR>
make[2]: *** [all-recursive] Error 1<BR>
make[2]: Leaving directory `/projects/geos-3.0.2/source/planargraph'<BR>
make[1]: *** [all-recursive] Error 1<BR>
make[1]: Leaving directory `/projects/geos-3.0.2/source'<BR>
make: *** [all-recursive] Error 1<BR>
<BR>
<BR>
Have to go to dinner now, but if you happen to get to it before I do, here is my revised patch.<BR>
<BR>
Mark - thanks for the vote of confidence. I almost feel like I know what I am doing :)<BR>
<BR>
Thanks,<BR>
Regina<BR>
<BR>
-----Original Message-----<BR>
From: geos-devel-bounces@lists.osgeo.org on behalf of Obe, Regina<BR>
Sent: Sun 10/19/2008 10:33 PM<BR>
To: PostGIS Development Discussion; PostGIS Development Discussion; geos-devel@lists.osgeo.org<BR>
Subject: [geos-devel] RE: [postgis-devel] 1, dot, 3 dot 4!<BR>
<BR>
Allright I'm working on it, but I don't have commit access so I'll just send you the revised patch when I am done.<BR>
<BR>
Thanks,<BR>
Regina<BR>
<BR>
-----Original Message-----<BR>
From: postgis-devel-bounces@postgis.refractions.net on behalf of Paul Ramsey<BR>
Sent: Sun 10/19/2008 9:33 PM<BR>
To: PostGIS Development Discussion<BR>
Subject: Re: [postgis-devel] 1, dot, 3 dot 4!<BR>
<BR>
Well, unless someone else (Mat?) can apply this patch back into 3.0<BR>
and test it, or you can work it up Regina, it'll have to wait until I<BR>
get home and set up a VM with a new debian in it that has the new gcc.<BR>
<BR>
P<BR>
<BR>
On Sun, Oct 19, 2008 at 4:06 PM, Obe, Regina <robe.dnd@cityofboston.gov> wrote:<BR>
> P,<BR>
> that got me further but no go. Seems to be same issue in an unpatched file<BR>
><BR>
> then mv -f ".deps/ByteOrderValues.Tpo" ".deps/ByteOrderValues.Plo";<BR>
> else rm -f ".deps/ByteOrderValues.Tpo"; exit 1; fi<BR>
> g++ -DHAVE_CONFIG_H -I. -I. -I../../source/headers<BR>
> -I../../source/headers/geos -I../../source/headers -g -O2 -DGEOS_INLINE<BR>
> -Wall -ansi -pedantic -Wno-long-long -MT ByteOrderValues.lo -MD -MP -MF<BR>
> .deps/ByteOrderValues.Tpo -c ByteOrderValues.cpp -fPIC -DPIC -o<BR>
> .libs/ByteOrderValues.o<BR>
> ByteOrderValues.cpp: In static member function 'static double<BR>
> geos::io::ByteOrderValues::getDouble(const unsigned char*, int)':<BR>
> ByteOrderValues.cpp:139: error: 'memcpy' was not declared in this scope<BR>
> ByteOrderValues.cpp: In static member function 'static void<BR>
> geos::io::ByteOrderValues::putDouble(double, unsigned char*, int)':<BR>
> ByteOrderValues.cpp:147: error: 'memcpy' was not declared in this scope<BR>
> make[2]: *** [ByteOrderValues.lo] Error 1<BR>
> make[2]: Leaving directory `/projects/geos-3.0.2/source/io'<BR>
> make[1]: *** [all-recursive] Error 1<BR>
> make[1]: Leaving directory `/projects/geos-3.0.2/source'<BR>
> make: *** [all-recursive] Error 1<BR>
><BR>
><BR>
> Thanks,<BR>
><BR>
> Regina<BR>
><BR>
><BR>
> -----Original Message-----<BR>
> From: postgis-devel-bounces@postgis.refractions.net on behalf of Paul Ramsey<BR>
> Sent: Sun 10/19/2008 5:14 PM<BR>
> To: PostGIS Development Discussion<BR>
> Subject: Re: [postgis-devel] 1, dot, 3 dot 4!<BR>
><BR>
> Yes, this has already been fixed on trunk, here's a patch against 3.0,<BR>
> let me know if it helps.<BR>
><BR>
> P.<BR>
><BR>
><BR>
> ________________________________<BR>
><BR>
> The substance of this message, including any attachments, may be<BR>
> confidential, legally privileged and/or exempt from disclosure pursuant to<BR>
> Massachusetts law. It is intended solely for the addressee. If you received<BR>
> this in error, please contact the sender and delete the material from any<BR>
> computer.<BR>
><BR>
> ________________________________<BR>
><BR>
> Help make the earth a greener place. If at all possible resist printing this<BR>
> email and join us in saving paper.<BR>
><BR>
> _______________________________________________<BR>
> postgis-devel mailing list<BR>
> postgis-devel@postgis.refractions.net<BR>
> <A HREF="http://postgis.refractions.net/mailman/listinfo/postgis-devel">http://postgis.refractions.net/mailman/listinfo/postgis-devel</A><BR>
><BR>
><BR>
_______________________________________________<BR>
postgis-devel mailing list<BR>
postgis-devel@postgis.refractions.net<BR>
<A HREF="http://postgis.refractions.net/mailman/listinfo/postgis-devel">http://postgis.refractions.net/mailman/listinfo/postgis-devel</A><BR>
<BR>
<BR>
<BR>
-----------------------------------------<BR>
The substance of this message, including any attachments, may be<BR>
confidential, legally privileged and/or exempt from disclosure<BR>
pursuant to Massachusetts law. It is intended<BR>
solely for the addressee. If you received this in error, please<BR>
contact the sender and delete the material from any computer.<BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>
<HTML><BODY><P><hr size=1></P>
<P><STRONG>
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.
</STRONG></P></BODY></HTML>
<P><hr size=1></P>
<P><STRONG><font size="2" color="339900"> Help make the earth a greener place. If at all possible resist printing this email and join us in saving paper. </p> <p> </font></STRONG></P>