From: | Tino Wildenhain <tino(at)wildenhain(dot)de> |
---|---|
To: | Nikhil Sontakke <nikhil(dot)sontakke(at)enterprisedb(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: cross-compiling plpython |
Date: | 2009-03-16 13:55:29 |
Message-ID: | 49BE5A51.9070803@wildenhain.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Nikhil Sontakke wrote:
> So, I realized that there does not seem to be an easy way for cross
> compiling plpython. The configure checks for the locally installed
> python include locations and eventually the plpython makefile ends up
> picking all the local includes too.
>
> Does anyone have any experiences on cross-compiling plpython before?
> Obviously I can hack the Makefile to point to the host environment
> headers, but is there a neater way? Also I suspect the plpython.so so
> generated might not load on the host later too because its looking for
> the libpython.so somewhere else too.
Did you check debian source packages? At least I believe they do not
compile everything on the respective system so there must be some hooks
for crosscompiling.
Regards
Tino
From | Date | Subject | |
---|---|---|---|
Next Message | Tomasz Olszak | 2009-03-16 14:16:07 | Problem with accesing Oracle from plperlu function when using remote pg client. |
Previous Message | Heikki Linnakangas | 2009-03-16 13:54:24 | Remaining items for 8.4 (was Re: Updates of SE-PostgreSQL 8.4devel patches (r1710)) |