[Python-Dev] Python build trouble with the new gcc/binutils

Andrew Koenig ark@research.att.com
Fri, 16 Aug 2002 13:34:05 -0400 (EDT)

Zack> On Fri, Aug 16, 2002 at 12:38:24PM -0400, Andrew Koenig wrote:

>> #0  __register_frame_info_bases (begin=0xfed50000, ob=0xfed50000, tbase=0x0, 
>> dbase=0x0) at /tmp/build1165/gcc-3.1.1/gcc/unwind-dw2-fde.c:83

Zack> Er, is the directory name misleading, or have you picked up
Zack> libgcc_s.so from 3.1.1?  In theory that shouldn't be a problem; in
Zack> practice it could well be the problem.

This particular test was done with gcc 3.1.1 and binutils 2.13.

As I said at the beginning of the discussion, if I use gcc 3.1.1
and binutils 2.12.1, the Python install works.  If I use gcc 3.2
*or* binutils 2.13, the Python install fails.