[geos-devel] GEOS-3.0.0rc1 in a week, SWIG status ?

[Michael Fuhr]

On Thu, Jul 06, 2006 at 01:35:59AM +0200, strk wrote:
> Charlie, we'll release the first candidate of GEOS in a week.

I just tried building GEOS CVS on Solaris 9 and got several undefined
symbol errors while linking capi/geostest.  I haven't built GEOS
CVS on Solaris for a long time so I don't know when this problem
started, but I have a libgeos-3.0.0.so from 16 Jan that appears to
work.

Here's what the linker complained about:

geos::index::bintree::NodeBase::addAllItems(std::vector<void*, std::allocator<void*> >*)
geos::index::bintree::NodeBase::addAllItemsFromOverlapping(geos::index::bintree::Interval*, std::vector<void*, std::allocator<void*> >*)
typeinfo for geos::index::bintree::NodeBase
geos::index::bintree::Interval::getMin() 
geos::index::bintree::Interval::getMax() 
geos::index::bintree::NodeBase::NodeBase()
geos::index::bintree::NodeBase::~NodeBase()
geos::index::bintree::Interval::getWidth() 
geos::index::bintree::NodeBase::nodeSize() 
geos::index::bintree::Interval::Interval(geos::index::bintree::Interval*)
geos::index::bintree::Interval::Interval()
geos::index::bintree::Interval::~Interval()
geos::index::bintree::Interval::Interval(double, double)
geos::index::bintree::NodeBase::add(void*)
geos::index::bintree::Root::insert(geos::index::bintree::Interval*, void*)
geos::index::bintree::NodeBase::size() 
geos::index::bintree::NodeBase::depth() 
geos::index::bintree::NodeBase::getItems() 

Earlier I see the following warnings and errors:

rm -fr .libs/libgeos.lax/libindex.a
mkdir .libs/libgeos.lax/libindex.a
(cd .libs/libgeos.lax/libindex.a && ar x /<path omitted>/source/index/.libs/libindex.a)
libtool: link: warning: object name conflicts; renaming object files
libtool: link: warning: to ensure that they will not overwrite
Mutually exclusive options were given!
Usage:  uniq [-c|-d|-u][-f fields][-s char] [input_file [output_file]]
Or:     uniq [-c|-d|-u][-n][+m] [input_file [output_file]]
../libtool: -r: is not an identifier

I see these messages only for libindex; other libraries build without
complaint.  uniq appears to be failing because of the options it's
passed.

I don't know much about libtool but it looks involved.  Any ideas?

-- 
Michael Fuhr