Bug 11978 - python-native is being built without IPV6 enabled
Summary: python-native is being built without IPV6 enabled
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: devtools / tool chain (show other bugs)
Version: 2.4
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 2.5 M1
Assignee: Alejandro Hernandez
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-08-25 02:46 UTC by Paul Eggleton
Modified: 2017-11-08 16:16 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: Regression (Used to work)
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Eggleton 2017-08-25 02:46:33 UTC
Since we introduced DISTRO_FEATURES_NATIVE, we have been building python-native with ipv6 disabled, which leads to the following issue on one of my systems:

------------ snip ------------
ERROR: python-paho-mqtt-1.3.0-r0 do_compile: python setup.py build execution failed.
ERROR: python-paho-mqtt-1.3.0-r0 do_compile: Function failed: do_compile (log file is located at /home/paul/poky/poky/build-minnow/tmp/work/corei7-64-poky-linux/python-paho-mqtt/1.3.0-r0
/temp/log.do_compile.36362)
ERROR: Logfile of failure stored in: /home/paul/poky/poky/build-minnow/tmp/work/corei7-64-poky-linux/python-paho-mqtt/1.3.0-r0/temp/log.do_compile.36362
Log data follows:
| DEBUG: Executing shell function do_compile
| Download error on https://pypi.python.org/simple/pytest-runner/: getsockaddrarg: bad family -- Some packages may not be found!
| Couldn't find index page for 'pytest-runner' (maybe misspelled?)
| Download error on https://pypi.python.org/simple/: getsockaddrarg: bad family -- Some packages may not be found!
| No local packages or working download links found for pytest-runner
| Traceback (most recent call last):
|   File "setup.py", line 55, in <module>
|     setup_requires=setup_requirements
|   File "/home/paul/poky/poky/build-minnow/tmp/work/corei7-64-poky-linux/python-paho-mqtt/1.3.0-r0/recipe-sysroot-native/usr/lib/python2.7/distutils/core.py", line 111, in setup
|     _setup_distribution = dist = klass(attrs)
|   File "build/bdist.linux-x86_64/egg/setuptools/dist.py", line 325, in __init__
|   File "build/bdist.linux-x86_64/egg/setuptools/dist.py", line 446, in fetch_build_eggs
|   File "build/bdist.linux-x86_64/egg/pkg_resources/__init__.py", line 855, in resolve
|   File "build/bdist.linux-x86_64/egg/pkg_resources/__init__.py", line 1127, in best_match
|   File "build/bdist.linux-x86_64/egg/pkg_resources/__init__.py", line 1139, in obtain
|   File "build/bdist.linux-x86_64/egg/setuptools/dist.py", line 518, in fetch_build_egg
|   File "build/bdist.linux-x86_64/egg/setuptools/command/easy_install.py", line 666, in easy_install
| distutils.errors.DistutilsError: Could not find suitable distribution for Requirement.parse('pytest-runner')
| ERROR: python setup.py build execution failed.
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_compile (log file is located at /home/paul/poky/poky/build-minnow/tmp/work/corei7-64-poky-linux/python-paho-mqtt/1.3.0-r0/temp/log.do_compile.36362)
ERROR: Task (/home/paul/poky/meta-openembedded/meta-python/recipes-devtools/python/python-paho-mqtt_1.3.0.bb:do_compile) failed with exit code '1'
------------ snip ------------

I'm unsure as to whether we want to add ipv6 to the default value for DISTRO_FEATURES_NATIVE or change python.inc to not look at DISTRO_FEATURES for it in the native case, but we do need to do something.
Comment 1 Paul Eggleton 2017-08-25 03:01:26 UTC
(One might ask why python-paho-mqtt is doing this stuff in do_compile, which is a legitimate question - but the bug still stands.)
Comment 2 Paul Eggleton 2017-09-14 05:57:14 UTC
I've filed bug 12084 to cover downloading during do_compile, so to be clear this bug is just about the ipv6 enablement issue for python(3)-native. (python3-native may not suffer from this exact failure but we should still be enabling ipv6 as appropriate, assuming it has the option to do so of course.)