Tom Lane wrote:
Well, we're not supporting dynamically linked objects in a static build ;-)
It's at least theoretically possible that you could link selected PL
objects into a static backend build, but no one is particularly
interested in expending effort on it. There don't seem to be any
pla
Am Donnerstag, 21. September 2006 16:02 schrieb Tom Lane:
> There don't seem to be any
> platforms anymore on which --disable-shared is actually important.
> (Should we just get rid of it?)
IIRC, I added it in the past to test for static-only platforms like QNX. I
don't know if we plan to suppor
Tom Lane wrote:
It's at least theoretically possible that you could link selected PL
objects into a static backend build, but no one is particularly
interested in expending effort on it. There don't seem to be any
platforms anymore on which --disable-shared is actually important.
(Should we just
"Albe Laurenz" <[EMAIL PROTECTED]> writes:
> Peter Eisentraut wrote:
>> Because createlang relies on *dynamic* loading.
> So that is working as designed.
> I interpret that as 'static builds for the database
> server are not supported'. Ok by me.
Well, we're not supporting dynamically linked obje
Peter Eisentraut wrote:
>> I notice that when I run 'make check' on a
>> statically linked HEAD, it fails during
>> 'createlang' with
>
> Because createlang relies on *dynamic* loading.
So that is working as designed.
I interpret that as 'static builds for the database
server are not supported'.
Albe Laurenz wrote:
> I notice that when I run 'make check' on a
> statically linked HEAD, it fails during
> 'createlang' with
Because createlang relies on *dynamic* loading.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)--
I notice that when I run 'make check' on a
statically linked HEAD, it fails during
'createlang' with
== installing plpgsql ==
ERROR: could not access file "$libdir/plpgsql": No such file or
directory
command failed:
"/postgres/cvs/pgsql/src/test/regress
