Bugs item #815999, was opened at 2003-10-01 17:21
Message generated for change (Comment added) made by gbrandl
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=815999&group_id=5470
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: Python 2.3
>Status: Pending
Resolution: None
Priority: 5
Submitted By: Peter Stauffert (stauffert)
Assigned to: Nobody/Anonymous (nobody)
Summary: ImportError: No module named _socket
Initial Comment:
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.3.1/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
----------------------------------------------------------------------
>Comment By: Georg Brandl (gbrandl)
Date: 2006-02-20 19:33
Message:
Logged In: YES
user_id=849994
OP: Do you still experience problems with 2.4?
----------------------------------------------------------------------
Comment By: Martin v. Löwis (loewis)
Date: 2003-10-13 21:27
Message:
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.
----------------------------------------------------------------------
Comment By: Jeremy Fincher (jemfinch)
Date: 2003-10-13 14:33
Message:
Logged In: YES
user_id=99508
If you don't mind, I'll just link you to my comp.lang.python
post about it:
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.
----------------------------------------------------------------------
Comment By: Anthony Baxter (anthonybaxter)
Date: 2003-10-13 05:51
Message:
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?
----------------------------------------------------------------------
Comment By: Jeremy Fincher (jemfinch)
Date: 2003-10-11 11:35
Message:
Logged In: YES
user_id=99508
I have this same bug on Solaris 7 with 2.3.2.
----------------------------------------------------------------------
Comment By: Anthony Baxter (anthonybaxter)
Date: 2003-10-04 00:24
Message:
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?
----------------------------------------------------------------------
Comment By: Martin v. Löwis (loewis)
Date: 2003-10-03 13:28
Message:
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???
----------------------------------------------------------------------
Comment By: casey dunn (caseyd)
Date: 2003-10-01 19:53
Message:
Logged In: YES
user_id=878394
I have seen this on Solaris as well, recent and old vintages.
Casey Dunn
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=815999&group_id=5470
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
