On Aug 1, 2011, at 3:54 PM, Mr. Puneet Kishor wrote:
Undefined symbols for architecture x86_64:
__ZNSt8auto_ptrIN4geos4geom8EnvelopeEEcvSt12auto_ptr_refIT_EIS2_EEv,
referenced from:
virtual thunk to
On Aug 2, 2011, at 7:00 AM, Howard Butler wrote:
On Aug 1, 2011, at 3:54 PM, Mr. Puneet Kishor wrote:
Undefined symbols for architecture x86_64:
__ZNSt8auto_ptrIN4geos4geom8EnvelopeEEcvSt12auto_ptr_refIT_EIS2_EEv,
referenced from:
virtual thunk to
On Aug 1, 2011, at 4:19 PM, Mr. Puneet Kishor wrote:
On Aug 2, 2011, at 7:00 AM, Howard Butler wrote:
Reported earlier [1].
I spent a little time trying to fix this, but I couldn't come up with a
solution.
The following works (the solution was listed in the MacPorts tickets) --
For whatever it's work (not much) the unit test failure seems to have
no reported knock-on effects in day-to-day use. So you can use the
GEOS code compiled with newer gcc without too much trepidation.
However, no luck in exterminating the test failure thus far.
P.
On Mon, Aug 1, 2011 at 2:33 PM,
I was kinda wondering if there was any real problem. I was compiling with gcc
4.2 for a while until I became aware of the test problem, and noone complained
directly about a CoordinateArraySequenceFactory problem with my GEOS framework.
On Aug 1, 2011, at 5:30 PM, Paul Ramsey wrote:
For
