Re: Re: PL/Python build

From: Mark Hollomon <mhh(at)mindspring(dot)com>
To: Joel Burton <jburton(at)scw(dot)org>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: PL/Python build
Date: 2001-05-10 19:26:07
Message-ID: 01051015260700.08996@jupiter.hollomon.fam
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wednesday 09 May 2001 19:02, Joel Burton wrote:
>
> One of the small problems of pl/python is going to similar to pl/perl...
> many linux distro's don't come with a shared object library for python,
> but come w/a static library only.
>
> pl/python will work w/a static library (if you uncomment the lines in the
> makefile to link all the modules against it directly); we can add a line
> to the faq about where packages, if any, are for python.so.

Be careful. That will only work if the static library contains relocatable
code so that the entire resulting library 'plpython.so' can be loaded
dynamically. From what I can tell, this is true on Linux, but not on say HPUX.
_That_ was the sticky point with pl/perl.

--
Mark Hollomon

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2001-05-10 19:43:28 Re: Regression tests for OBSD scrammed..
Previous Message Peter Eisentraut 2001-05-10 18:32:54 Re: Paths for C functions (was Re: Re: backend dies on 7.1.1 loading large datamodel.)