Palle Girgensohn schrieb:
I'm not a linking guru... Is there a penalty for setting LDFLAGS+=
-lstdc++ when building postgresql?
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.
A
On Thu, Nov 18, 2004 at 04:17:31AM +0100, Palle Girgensohn wrote:
> Does the same arguments apply for linking with libc_r (pthreads)?
>
> It is needed by plpython, at least on FreeBSD 4.10 (probably all versions).
There are problem with libc_r on FreeBSD: due to initializing
of red zone for init
Does the same arguments apply for linking with libc_r (pthreads)?
It is needed by plpython, at least on FreeBSD 4.10 (probably all versions).
/Palle
--On onsdag, november 17, 2004 20.49.20 -0500 Tom Lane <[EMAIL PROTECTED]>
wrote:
Palle Girgensohn <[EMAIL PROTECTED]> writes:
Is there a penalty in
Palle Girgensohn <[EMAIL PROTECTED]> writes:
>> Is there a penalty in just leaving
>> LDFLAGS+= -lstdc++
>> in the postgresql port Makefile? Bad idea?
Yup. The portability hazards are considerable. I'm a bit surprised the
postgis guys seem to think it works.
regards, tom
Hi!
I'm not a linking guru... Is there a penalty for setting LDFLAGS+= -lstdc++
when building postgresql?
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 do
