[Python-bugs-list] [ python-Bugs-454493 ] building _socket failed

[noreply@sourceforge.net]

Bugs item #454493, was opened at 2001-08-23 00:44
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=454493&group_id=5470

Category: Extension Modules
Group: Python 2.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Roeland Rengelink (rengelink)
Assigned to: Martin v. Löwis (loewis)
Summary: building _socket failed

Initial Comment:
I experienced a build failure of Python2.2a2 on Suse
6.4 Linux 2.2.14

The following error was reported:

gcc -DINET6 -g -O3 -Wall -Wstrict-prototypes -fPIC -I.
-I~/Python-2.2a2/./Include -I/usr/local/include
-IInclude/ -c ~/Python-2.2a2/Modules/socketmodule.c -o
build/temp.linux-i686-2.2/socketmodule.o
~/Python-2.2a2/Modules/socketmodule.c: In function
`makesockaddr':
~/Python-2.2a2/Modules/socketmodule.c:715: structure
has no member named `sin6_scope_id'
~/Python-2.2a2/Modules/socketmodule.c: In function
`getsockaddrarg':
~/Python-2.2a2/Modules/socketmodule.c:828: structure
has no member named `sin6_scope_id'
~/Python-2.2a2/Modules/socketmodule.c: In function
`PySocket_getnameinfo':
~/Python-2.2a2/Modules/socketmodule.c:2469: structure
has no member named `sin6_scope_id'
WARNING: building of extension "_socket" failed:
command 'gcc' failed with exit status 1

I didn't see this in 2.2a1. Presumably, there is a
problem with IPv6 support on my machine. Shouldn't
configure have cought this?

Probably also a bug is that test_socket ran
succesfully. Since _socket wasn't build, the old
version in $PREFIX/lib/Python2.2/, which I got from
2.2a1, was used in the test.

Let me know if you need additional info.

Roeland

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

>Comment By: Martin v. Löwis (loewis)
Date: 2001-09-04 05:01

Message:
Logged In: YES 
user_id=21627

Please try the attached config.patch (contributed by
itojun). It is against 2.2a2; if you want to apply it to any
other Python snapshot, you need to rerun autoconf. It should
detect that your C library does not support the RFC2553 API
(despite being glibc), and thus disable IPv6 support.

Please report whether it works, and if not, report how
you've invoked configure, and what version of the C library
you have. If you then need a work-around, try configuring
with --disable-ipv6 (this should not be necessary with the
patch).

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

Comment By: Guido van Rossum (gvanrossum)
Date: 2001-08-23 07:39

Message:
Logged In: YES 
user_id=6380

Oh well. Maybe you built 2.2a2 in the same directory as
2.2a1?

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

Comment By: Roeland Rengelink (rengelink)
Date: 2001-08-23 07:33

Message:
Logged In: YES 
user_id=302601

Re test_socket failing to fail. You can mark that as
irreproducable. I completely deleted my old Python installs
and then did an Install of 2.2a1 followed by a build of
2.2a2. make test now failed on test__all__ with

test test___all__ skipped --  No module named _socket

and on test_socket with

test test_socket crashed -- exceptions.AttributeError:
'module' object has no attribute 'error'

I am of course convinced that this didn't happen last time
;)
Sorry for bothering you with that one.

(the build failure stands, I'm not going crazy yet)

Roeland



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

Comment By: Guido van Rossum (gvanrossum)
Date: 2001-08-23 06:21

Message:
Logged In: YES 
user_id=6380

Thanks for the report.  I've assigned this to the IPv6
author.  He's on vacation, but will look at this when he's
back in a week or so.

Re test_socket succeeding: did you run it from the build
directory, or did you install the broken installation? If
the latter, you have yourself to blame. If the former, I'd
like to see the value of sys.path and all env variables
starting with PYTHON (try "set | grep PYTHON" in your shell)
to help you debug this.

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

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