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

Zack Weinberg zack@codesourcery.com
Fri, 16 Aug 2002 10:28:59 -0700

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

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

> #1  0xfed517ec in frame_dummy ()
>    from /export/spurr1/homes1/ark/Python-2.2.1/build/lib.solaris-2.7-sun4u-2.2/struct.so
> #2  0xfed516d4 in _init ()
>    from /export/spurr1/homes1/ark/Python-2.2.1/build/lib.solaris-2.7-sun4u-2.2/struct.so
> #3  0xff3bc174 in ?? ()
> #4  0xff3c0a8c in ?? ()
> #5  0xff3c0ba8 in ?? ()
> #6  0x0007b384 in _PyImport_GetDynLoadFunc (fqname=0x2 <Address 0x2 out of bounds>, 
>     shortname=0x1002c8 "", 
>     pathname=0xffbedbd8 "/export/spurr1/homes1/ark/Python-2.2.1/build/lib.solaris-2.7-sun4u-2.2/struct.so", fp=0xfc1d8) at Python/dynload_shlib.c:90

Can you disable all use of dynamic loading and try the build again?
Unfortunately, the only practical way to do this seems to be to edit
configure.in and force DYNLOADFILE to be dynload_stub.o (right before
the line saying AC_MSG_RESULT($DYNLOADFILE)), then regenerate
configure.  (Might be a good idea to add an --enable switch.)

This will obviously not get you an installable build, but it will let
us narrow down the problem a bit.