Re: cross-compiling plpython - Mailing list pgsql-hackers

From Tino Wildenhain
Subject Re: cross-compiling plpython
Date
Msg-id 49BE5A51.9070803@wildenhain.de
Whole thread Raw
In response to cross-compiling plpython  (Nikhil Sontakke <nikhil.sontakke@enterprisedb.com>)
Responses Re: cross-compiling plpython  (Nikhil Sontakke <nikhil.sontakke@enterprisedb.com>)
Re: cross-compiling plpython  (Peter Eisentraut <peter_e@gmx.net>)
List 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

pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Remaining items for 8.4 (was Re: Updates of SE-PostgreSQL 8.4devel patches (r1710))
Next
From: Tomasz Olszak
Date:
Subject: Problem with accesing Oracle from plperlu function when using remote pg client.