[Python-bugs-list] [ python-Bugs-815753 ] SCO_SV: many modules cannot be imported

SourceForge.net noreply at sourceforge.net
Fri Oct 3 08:37:38 EDT 2003


Bugs item #815753, was opened at 2003-10-01 12:31
Message generated for change (Comment added) made by eurosys
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=815753&group_id=5470

Category: Build
Group: Python 2.3
Status: Open
Resolution: None
Priority: 5
Submitted By: Roger Erens (eurosys)
Assigned to: Nobody/Anonymous (nobody)
Summary: SCO_SV: many modules cannot be imported

Initial Comment:
Trying to execute the makefile for Python 2.3.1 and 2.3.

2c on an SCO-box results in a lot of warnings like:



*** WARNING: importing extension "struct" failed with 

exceptions.AttributeError:

 'module' object has no attribute 'load_dynamic'



This results in not being able to import the struct (and 

many others) module in the Python interpreter:



Python 2.3.2c1 (#7, Oct  1 2003, 12:08:43) [C] on 

sco_sv3

Type "help", "copyright", "credits" or "license" for more 

information.

>>> import struct

Traceback (most recent call last):

  File "<stdin>", line 1, in ?

ImportError: No module named struct



See the attached make.out file, which includes the 

generated makefile for my system, followed by the output 

sent to stdout.



Installing Python 2.2.3 went almost flawless.





>uname -X



System = SCO_SV

Node = ontwik2

Release = 3.2v5.0.5

KernelID = 98/07/02

Machine = i80386

BusType = ISA

Serial = 5FL004745

Users = 30-user

OEM# = 0

Origin# = 1

NumCPU = 2



----------------------------------------------------------------------

>Comment By: Roger Erens (eurosys)
Date: 2003-10-03 14:37

Message:
Logged In: YES 
user_id=878033

Hi Michael,



nice hack for a first time: no warnings this time, as you can 

see in the attached make.out. Thanks a lot!



Only a few compiler errors remain, but I cannot be bothered 

with them right now. So just FYI (after running make; make 

clean):



>make > make.out

"Objects/stringobject.c", line 1765: warning: statement not 

reached

"/usrdir/rogere/Python-2.3.2c1/Modules/getaddrinfo.c", line 

556: error: undefine

d symbol: h_errno

"/usrdir/rogere/Python-2.3.2c1/Modules/getnameinfo.c", line 

184: error: undefine

d symbol: h_errno

"/usrdir/rogere/Python-2.3.2c1/Modules/socketmodule.c", line 

2374: error: undefi

ned symbol: h_errno

"/usrdir/rogere/Python-2.3.2c1/Modules/socketmodule.c", line 

2972: error: undefi

ned symbol: AF_INET6

"/usrdir/rogere/Python-2.3.2c1/Modules/socketmodule.c", line 

3016: error: undefi

ned symbol: INET_ADDRSTRLEN

"/usrdir/rogere/Python-2.3.2c1/Modules/socketmodule.c", line 

3016: error: integr

al constant expression expected

"/usrdir/rogere/Python-2.3.2c1/Modules/socketmodule.c", line 

3055: warning: stat

ement not reached

"/usrdir/rogere/Python-2.3.2c1/Modules/_cursesmodule.c", line 

1553: warning: arg

ument is incompatible with prototype: arg #1

"/usrdir/rogere/Python-2.3.2c1/Modules/_cursesmodule.c", line 

1554: warning: arg

ument is incompatible with prototype: arg #1

"/usrdir/rogere/Python-2.3.2c1/Modules/_cursesmodule.c", line 

1964: warning: ass

ignment type mismatch



----------------------------------------------------------------------

Comment By: Michael Hudson (mwh)
Date: 2003-10-03 13:17

Message:
Logged In: YES 
user_id=6656

Curioser and curioser.  The difference seems to be that

configure for 2.2.3 passes "-belf" to cc when checking for

dlopen but configure for 2.3 doesn't.



I actually have an idea how this happens: in 2.3, the CFLAGS

variable was split up into BASECFLAGS and OPT.  We know we

need -belf on SCO, so we stuff that into BASECFLAGS. 

However, this *doesn't* make the rest of the configure tests

use -belf -- result breakage.



(Martin, are you reading this?  Does this sound reasonable?)



Roger, can you try the attached patch?  It's a bit of a hack...

----------------------------------------------------------------------

Comment By: Roger Erens (eurosys)
Date: 2003-10-03 00:25

Message:
Logged In: YES 
user_id=878033

I uploaded both the config.log and the pyconfig.h for 2.2.3.

I'm curious what you think of it. The system is quite old, 

indeed (but we have even older among our customer base, as 

they are not very much inclined to investing in hardware!).

It is much used, though.



Regards,

Roger

----------------------------------------------------------------------

Comment By: Michael Hudson (mwh)
Date: 2003-10-01 18:19

Message:
Logged In: YES 
user_id=6656

Can you attach the config.log for 2.2.3?  I'm now a little

curious as to how dynamic linking ever worked on this system

(which is fairly old, right?)

----------------------------------------------------------------------

Comment By: Roger Erens (eurosys)
Date: 2003-10-01 17:45

Message:
Logged In: YES 
user_id=878033

Got to go home now. Hope I can help you further tomorrow.

-RE-

----------------------------------------------------------------------

Comment By: Anthony Baxter (anthonybaxter)
Date: 2003-10-01 17:34

Message:
Logged In: YES 
user_id=29957

Hm. mwh is right - it seems like HAVE_DYNAMIC_LOADING isn't

being defined. Could you also attach the files configure.log

and pyconfig.h from the 2.3 build?



----------------------------------------------------------------------

Comment By: Michael Hudson (mwh)
Date: 2003-10-01 17:10

Message:
Logged In: YES 
user_id=6656

It looks like the module 'imp' is messed up.  That's strange.

----------------------------------------------------------------------

Comment By: Anthony Baxter (anthonybaxter)
Date: 2003-10-01 16:43

Message:
Logged In: YES 
user_id=29957

Ugh. I don't have access to any SCO boxes to debug this.

Could you rebuild Python 2.2 on the same platform and attach

the output (as you did for 2.3). Obviously something's

changed in how we invoke the dynamic linker or some such.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=815753&group_id=5470



More information about the Python-bugs-list mailing list