From owner-freebsd-ports@FreeBSD.ORG Tue Oct 5 15:33:10 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2675516A524 for ; Tue, 5 Oct 2004 15:33:10 +0000 (GMT) Received: from bloodwood.hunterlink.net.au (smtp-local.hunterlink.net.au [203.12.144.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9471243D2F for ; Tue, 5 Oct 2004 15:33:08 +0000 (GMT) (envelope-from boris@brooknet.com.au) Received: from ppp2527.dyn.pacific.net.au (ppp2527.dyn.pacific.net.au [61.8.37.39])i95FU9Aj007872; Wed, 6 Oct 2004 01:30:11 +1000 From: Sam Lawrance To: Anderson Soares Ferreira , Palle Girgensohn Content-Type: text/plain Date: Wed, 06 Oct 2004 01:34:59 +1000 Message-Id: <1096990499.13152.18.camel@dirk.no.domain> Mime-Version: 1.0 X-Mailer: Evolution 2.0.1FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit cc: ports@freebsd.org Subject: postgresql build options, postgis and geos X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Oct 2004 15:33:10 -0000 Hi folks, Just a quick prod to see what you think... Postgis includes a bunch of useful functions for manipulating spatial data. Some of them are provided by geos, a separate c++ library, with postgis providing wrappers. According to postgis docs, postgresql _must_ be configured with LDFLAGS containing -lstdc++ for this to work. I can confirm this. The postgis port provides the WITH_GEOS tunable, but it has no effect unless the above adjustment is made to postgresql. The port makes no mention of this. Is there a penalty in just leaving LDFLAGS+= -lstdc++ in the postgresql port Makefile? Bad idea? What do you think? Regards Sam