| From: | Nikhil Sontakke <nikhil(dot)sontakke(at)enterprisedb(dot)com> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | cross-compiling plpython |
| Date: | 2009-03-16 09:07:11 |
| Message-ID: | a301bfd90903160207r35145d4dhf5d01ce5b9d80912@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
Regards,
Nikhils
--
http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2009-03-16 10:08:06 | Re: Review: B-Tree emulation for GIN |
| Previous Message | Simon Riggs | 2009-03-16 08:46:33 | Re: How to implement an auto-increment column for a system catalog table? |