Hi

There is a problem during the installation of python 2.3.1:

I used configure with the following options:
./configure --enable-shared=yes --with-signal-
module=yes --with-cxx=/usr/freeware/bin/c++

make runs to the end, only warning messages are 
displayed.

Running "make test" on a SGI Origin200, IRIX 6.5-18 I 
got the following error message:
test test___all__ failed -- Traceback (most recent call 
last):
  File "/install/fw/Python-2.Lib/test/test___all__.py", 
line 54, in test_all
    import _socket
ImportError: No module named _socket

This looks like the python bug 565710 reported for 
python 2.2.1 which was solved by modifications of 
setup.py in the top level directory.

But setup.py was modified in python 2.3.1 and I could 
not apply the old patch to the new version.

Could you help me with this problem?

Thanks a lot

Peter Stauffert

Logged In: YES 
user_id=878394

I have seen this on Solaris as well, recent and old vintages.

Casey Dunn

Logged In: YES 
user_id=21627

Can you please attach the build log? In particular, it would
be importing to see whether building _socket was attempted,
and failed.

Maybe your compiler just doesn't work???

Logged In: YES 
user_id=29957

Does the patch available from www.python.org/bugs.html fix
this problem?

Which compiler did you use? From the configure line, above,
it looks like you might be using gcc?

Logged In: YES 
user_id=99508

I have this same bug on Solaris 7 with 2.3.2.

Logged In: YES 
user_id=29957

Works for me on Solaris 2.6, 7 and 8. What compiler, what
version, what error did you get during the build of
socketmodule?

Logged In: YES 
user_id=99508

If you don't mind, I'll just link you to my comp.lang.python
post about it:

0310100915.359b2e09%40posting.google.com&rnum=9">http://groups.google.com/groups?q=group:comp.lang.python+solaris+7&hl=en&lr=&ie=UTF-8&oe=UTF-8&selm=698f09f8.0310100915.359b2e09%40posting.google.com&rnum=9

That has the exact compilation error.  I've tried passing
the --disable-IPV6 option to configure (as MvL mentioned)
and it seemed to compile, but I still don't have access to
the _socket library, probably due to the second error I
mentioned.  I tried the fix in the bug #565710 (adding
runtime_library_dirs to setup.py) but to no avail.

Logged In: YES 
user_id=21627

jemfinch, I very much doubt that you have the same problem
as the submitter of this report, and your Usenet message
gives hardly enough detail to analyse the problem; for
example, the linker error you report has a truncated error
message. Please submit a separate report, and report
precisely what you did, the complete output that you got,
and what exactly isn't working the way you expect it to work.

Logged In: YES 
user_id=849994

OP: Do you still experience problems with 2.4?

Logged In: YES 
user_id=1312539

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).