[geos-devel] Re: freeBSD ports GEOS

strk at refractions.net strk at refractions.net
Sun Dec 11 18:49:12 EST 2005

[geos-devel included]

On Sat, Dec 10, 2005 at 08:30:09PM +0100, strk at refractions.net wrote:
> On Sat, Dec 10, 2005 at 07:39:44PM +0100, Konstantin Saurbier wrote:
> > Stephen Woodbridge wrote on Sat Dec 10, 2005 um 01:34:03PM:
> > > Hello,
> > > 
> > > I got you email from the freeBSD geos package as the port maintainer.
> > > 
> > > I use PostGIS which depends on GEOS and I have had a problem with the last two 
> > > upgrades, GEOS-2.1.4 and GEOS-2.2.0 in that these have created libraries of 
> > > libgeos.so.3 and libgeos.so.4 respectively. The problem is that these should 
> > > probably both be libgeos.so.2. Well at least PostGIS expects the library to be 
> > > libgeos.so.2.
> > > 
> > > I have copied Strk the GEOS developer who might have more to comment on this.
> > > 
> > > Any help with this would be appreciated by all freeBSD users of these packages.
> > 
> > Have you tried to just create appropiate links? For example:
> > 
> > ln -s libgeos.so.4 libgeos.so.3
> > 
> > if this will fix your problems i will patch geos to create these links at
> > installtime.
> > Be adviced that geos will not compile on FreeBSD 4.x. I will contact the
> > GEOS developers later on, but i had no time until now.
> I have access to a FreeBSD 4.2 - I'll test this and let you know.

I successfully build 2.2.1 (out tomorrow) with g++ (GCC) 3.4.4.
I confirm that libgeos.so comes out versioned as .4 (libgeos.so.4)
SONAME sems to be libgeos.so.4 but didn't have readelf(1) available
to check this.

I assume this is a decision taken by libtool, probably due to
requirements of the FreeBSD dynamic linker. Basically it looks
like on Linux an addition of interfaces (in libtool terms) is binary
compatible while in FreeBSD it is not.

Mea culpa: I shouldn't have incremented INTERFACE_CURRENT for C++
lib as there really haven't been any additional interface there.
I wanted to encode addition of the C-API, but that should have
been reflected on release version only, not C++ library SONAME.

The symlink should work fine (as no binary breaks has been introduced),
but its really not that clean and should be avoided in future.


 /"\    ASCII Ribbon Campaign
 \ /    Respect for low technology.
  X     Keep e-mail messages readable by any computer system.
 / \    Keep it ASCII. 

More information about the geos-devel mailing list