On 10/15/07, Peter Eisentraut [EMAIL PROTECTED] wrote:
Tom Lane wrote:
I notice though that the
second of the above-mentioned patches is only in HEAD, which is why
those same machines are giving scary-looking warnings in the 8.2
branch, eg wasp on 8.2:
The CVS log message for that says
Am Montag, 15. Oktober 2007 schrieb Marko Kreen:
The CVS log message for that says Allow PL/PythonU to compile on Python
2.5., but that is evidently not true. Is this just a warning cleanup,
or is there perhaps a 32 vs 64 bit issue that is being fixed there?
It's a crash fix for 64bit
I noticed that two of the buildfarm members are failing the 8.1 branch
because they're trying to build plpython with python 2.5. To get that
to work, I think we'd need to back-patch these two fixes:
http://archives.postgresql.org/pgsql-committers/2006-11/msg00165.php
Tom Lane wrote:
I noticed that two of the buildfarm members are failing the 8.1
branch because they're trying to build plpython with python 2.5. To
get that to work, I think we'd need to back-patch these two fixes:
http://archives.postgresql.org/pgsql-committers/2006-11/msg00165.php
Peter Eisentraut [EMAIL PROTECTED] writes:
Tom Lane wrote:
I noticed that two of the buildfarm members are failing the 8.1
branch because they're trying to build plpython with python 2.5. To
get that to work, I think we'd need to back-patch these two fixes:
Tom Lane wrote:
I notice though that the
second of the above-mentioned patches is only in HEAD, which is why
those same machines are giving scary-looking warnings in the 8.2
branch, eg wasp on 8.2:
The CVS log message for that says Allow PL/PythonU to compile on Python
2.5., but that is
