curses, python20/152, RH70/62, postgresql problems

[D-Man]

On Fri, Jan 19, 2001 at 03:18:16AM +0000, A.M. Kuchling wrote:
| Let's tackle these one by one.
| On Thu, 18 Jan 2001 15:44:49 GMT, dubal at my-deja.com <dubal at my-deja.com> wrote:
| >We then tried to compile Py20 source on RH7. It
| >gives some LONG_BIT error and stops.
| 
| This is not a GCC problem; it is a glibc problem.  Red Hat has
| released an updated RPM for glibc, so installing it should let you
| compile Python 2.0 without difficulty.  Trying to use kgcc wouldn't
| help, because it's not the compiler's fault.
| 

Could you provide some more details on the glibc problem?  I used to
have RH7 and didn't find anything obviously wrong in the headers, so I
assumed it was the compiler that wasn't doing the comparison
correctly.  I solved the problem by manually editing the header (
<bits/xopen_lim.h> ).  I have since upgraded to Debian, but am still
curious.

Basically, for RH7 users : you can't use any rpms that people provide.
RH used an incompatible compiler, so you must compile stuff yourself.
(Or find RH7 specific rpms)  Also note that stuff compiled with newer
versions of gcc (3.0 when it is released) for newer dists (I assume RH
will use 3.0 when it is released) won't work on RH7 either.  Rpms made
for RH7 or RH6 (or anything older) won't work on the a dist with the
new compiler.

-D