Am Montag, 4. September 2006 04:06 schrieb Andrew Dunstan:
Patch attached - seems to work on my FC5/x86_64 box. Also contains the
OSX fix backported. Not sure that it qualifies as small though :-)
It looks pretty scary to me.
Didn't we say once that we don't want to backport fixes for
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
Peter Eisentraut wrote:
Ideally, we would get Python to tell us the right location, because use lib64
if it exists isn't the right solution.
Is this fixed somewhere post 7.4?
Yes, but it was never backported.
Andrew Dunstan [EMAIL PROTECTED] writes:
Peter Eisentraut wrote:
Ideally, we would get Python to tell us the right location, because use
lib64
if it exists isn't the right solution.
Is this fixed somewhere post 7.4?
Yes, but it was never backported. See:
I see that my new 64 bit / FC5 buildfarm member died on building 7.4
due to the following line in the configure script:
python_configdir=${python_execprefix}/lib/python${python_version}/config
On my machine, this should be lib64, not lib. In fact, both
/usr/lib/python2.4 and
Am Dienstag, 29. August 2006 16:25 schrieb Andrew Dunstan:
On my machine, this should be lib64, not lib. In fact, both
/usr/lib/python2.4 and /usr/lib64/python2.4 exist, so I can't just use a
soft link to get around this.
Ideally, we would get Python to tell us the right location, because use
Andrew Dunstan wrote:
I see that my new 64 bit / FC5 buildfarm member died on building 7.4
due to the following line in the configure script:
python_configdir=${python_execprefix}/lib/python${python_version}/config
On my machine, this should be lib64, not lib. In fact, both
Peter Eisentraut wrote:
Am Dienstag, 29. August 2006 16:25 schrieb Andrew Dunstan:
On my machine, this should be lib64, not lib. In fact, both
/usr/lib/python2.4 and /usr/lib64/python2.4 exist, so I can't just use a
soft link to get around this.
Ideally, we would get Python to tell us