[Python-bugs-list] [ python-Bugs-414371 ] bad gcc/glibc config
noreply@sourceforge.net
noreply@sourceforge.net
Sat, 07 Apr 2001 13:03:40 -0700
Bugs item #414371, was updated on 2001-04-06 12:26
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=414371&group_id=5470
Category: Build
>Group: 3rd Party
>Status: Closed
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: bad gcc/glibc config
Initial Comment:
When attempting to build version 2.1(b2a) on a RedHat
7.0 system (upgraded to kernel 2.4.3, glibc 2.2-12, and
libstc 2.96-69) package failed to make. Previous
version of 2.0 also failed at this point but I elected
to use 1.5 rather than resolve the problem.
After 'make' the following was wrote to the terminal:
gcc -c -g -O2 -Wall -Wstrict - prototypes -I.
-I./Include -DHAVE_CONFIG_H -o Modu{...]
In file included from Include/Python.h:54, from
Modules/python.c:3:
Include/pyport.h:422:2: #error "LONG_BIT definition
appears wrong for platform (bad gcc/glibc config)[...]
make: *** {Modules/python.o] Error 1 [End Error] So no
build and no Python 2. ||
Hardware specs: PIII, 256 MB Ram, 20 GB HD, used as a
development platform.
----------------------------------------------------------------------
Comment By: Tim Peters (tim_one)
Date: 2001-04-07 13:03
Message:
Logged In: YES
user_id=31435
The GCC version that comes with Red Hat 7.0 is not fit for
distribution.
In particular, it defines LONG_BIT as 64 on 32-bit machines under
certain circumstances, and letting this go unchecked would cause
it to generate bad code for various Python arithmetic operations.
The solution is to download a valid version of GCC.
See
http://www.python.org/cgi-
bin/moinmoin/FrequentlyAskedQuestions#line53
for more information.
----------------------------------------------------------------------
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=414371&group_id=5470