[Patches] [ python-Patches-617906 ] Build Error on Systems Without IPv6 Supp

[noreply@sourceforge.net]

Patches item #617906, was opened at 2002-10-03 06:20
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=305470&aid=617906&group_id=5470

Category: Build
Group: Python 2.2.x
Status: Open
Resolution: None
Priority: 5
Submitted By: Kurt B. Kaiser (kbk)
Assigned to: Nobody/Anonymous (nobody)
Summary: Build Error on Systems Without IPv6 Supp

Initial Comment:
The problem was discovered installing 2.2.1
from the src.rpm on a Redhat 6.2 system
which does not have IPv6 support.

The 17 Sept 02 revision of python-2.2.spec
(2.2.1-2) defaults to building Python with the
configure switch --enable-ipv6=yes.

An AC_ARG_ENABLE macro in configure.in
sets ENABLE_IPV6 if the config switch is set,
without checking whether the system has the
resources to build and run IPv6.  This forces a
compile with IPV6 support which fails on my
system.  Python then ends up without any 
socket support since .../lib-dynload/_socket.so
is missing.

Among other problems, this AC_ARG_ENABLE
logic re-exposes Bug 454493.

For clarity, the patch is provided in three stages,
meant to be applied in sequence:

1. configure.in.patch1 supplies the minimum to 
move the AF_INET6 and RFC2553 tests out of
the ACTION_IF_NOT_GIVEN section of the
macro.  A default of no IPv6 support is supplied.

2. configure.in.patch2 integrates the stack type
and IPv6 library presence tests into the logic
which sets ENABLE_IPV6.  Trace messages are
added to the test for IPv6 library presence.  The
logic is changed so that the build will default to 
IPv4 instead of exiting the configuration process
if the IPv6 library is not found.  IPv6 support is
compiled only if the system passes all the tests.
Finally, some comments in the stack type check are
changed to allow them to appear in configure as
well as configure.in.

3. configure.in.patch3 does whitespace normalization
for this section of configure.in.

This patch may solve the problem raised in Bug 
553000; I experienced shell errors testing the various
paths through the stack type check / library check 
until I quoted the shell variables in the library check.

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

>Comment By: Martin v. Löwis (loewis)
Date: 2002-10-03 17:53

Message:
Logged In: YES 
user_id=21627

I fail to see the bug being fixed. An explicit --enable-ipv6
is meant to request explicitly request IPv6 support,
overriding the automatic test that happens if you don't
provide an option.

So the right solution appears to be to change the spec file.
I don't know where you got that spec file from, so I can't
help here.

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

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