python build/Current CVS/UnixWare

Larry Rosenman writes:

In the current CVS, the PYTHON build sets LDSHARED to ld -G, not
cc -G. It passes -Wl,-h,... to the ld command, and breaks.

ALL shared library builds on UnixWare should use cc -G or CC -g as
appropriate.

I have arranged for the -Wl,-h to be left out in the Python build. The ld
vs cc thing you have to take up with the Python folks. I'm not convinced
their infrastructure works too well. For example, we might have to pull
the same kludge as we do for the Perl interface build on some platforms.

Eventually we might be able to write our own rules for this and not use
the Python build infrastructure. Not now, though.

--
Peter Eisentraut peter_e@gmx.net http://yi.org/peter-e/

I submitted a bug to their SourceForge Bug List.

Thanks!

LER

-----Original Message-----
From: Peter Eisentraut [mailto:peter_e@gmx.net]
Sent: Wednesday, February 07, 2001 12:34 PM
To: Larry Rosenman
Cc: PostgreSQL Hackers List
Subject: Re: python build/Current CVS/UnixWare

Larry Rosenman writes:

In the current CVS, the PYTHON build sets LDSHARED to ld -G, not
cc -G. It passes -Wl,-h,... to the ld command, and breaks.

ALL shared library builds on UnixWare should use cc -G or CC -g as
appropriate.

I have arranged for the -Wl,-h to be left out in the Python build. The ld
vs cc thing you have to take up with the Python folks. I'm not convinced
their infrastructure works too well. For example, we might have to pull
the same kludge as we do for the Perl interface build on some platforms.

Eventually we might be able to write our own rules for this and not use
the Python build infrastructure. Not now, though.

--
Peter Eisentraut peter_e@gmx.net http://yi.org/peter-e/