| Summary: | building python-qpid-proton fails under rh-python34 | ||
|---|---|---|---|
| Product: | Red Hat Software Collections | Reporter: | Matthew Farrellee <matt> |
| Component: | rh-python34 | Assignee: | Robert Kuska <rkuska> |
| Status: | CLOSED UPSTREAM | QA Contact: | BaseOS QE - Apps <qe-baseos-apps> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | unspecified | CC: | bkabrda, dingham, jberan, jross, kgiusti, matt, rkuska |
| Target Milestone: | alpha | ||
| Target Release: | 2.2 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-03-02 14:46:38 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Matthew Farrellee
2016-02-27 17:02:25 UTC
I've checked prelinked libraries of python binary: [root@deimos /]# ldd /opt/rh/rh-python34/root/usr/bin/python linux-vdso.so.1 => (0x00007ffc16872000) libpython3.4m.so.rh-python34-1.0 => /opt/rh/rh-python34/root/usr/lib64/libpython3.4m.so.rh-python34-1.0 (0x00007fddeb0e8000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fddeaec5000) libdl.so.2 => /lib64/libdl.so.2 (0x00007fddeacc1000) libutil.so.1 => /lib64/libutil.so.1 (0x00007fddeaabe000) libm.so.6 => /lib64/libm.so.6 (0x00007fddea7bb000) libc.so.6 => /lib64/libc.so.6 (0x00007fddea3fa000) /lib64/ld-linux-x86-64.so.2 (0x0000563bd0b4c000) Also checked user rights and if the library mentioned above exists: [root@deimos /]# ls -l /opt/rh/rh-python34/root/usr/lib64/libpython3.4m.so.rh-python34-1.0 -rwxr-xr-x. 1 root root 2594992 Mar 25 2015 /opt/rh/rh-python34/root/usr/lib64/libpython3.4m.so.rh-python34-1.0 LD_LIBRARY_PATH seems to be also correct: [root@deimos /]# echo $LD_LIBRARY_PATH /opt/rh/rh-python34/root/usr/lib64 Diggin into this deeper this seems to be python-qpid-proton issue as it does modify environment variables.
See its setup.py@183
subprocess.Popen([sys.executable, os.path.join(proton_src, 'protocol.h.py')],
env={'PYTHONPATH': proton_base}, stdout=header)
env override our LD_LIBRARY_PATH variable, see:
>>> subprocess.Popen('/usr/bin/echo $LD_LIBRARY_PATH', shell=True, env={'PYTHONPATH': '.'}, stdout=subprocess.PIPE).stdout.read()
b'\n'
>>> subprocess.Popen('/usr/bin/echo $LD_LIBRARY_PATH', shell=True, stdout=subprocess.PIPE).stdout.read()
b'/opt/rh/rh-python34/root/usr/lib64\n'
Correct way for qpid proton to handle env variables is to pass os.environ.copy() with modified 'PYTHONPATH' (according their needs).
I will submit PR to upstream.
Possible workaround for you could be `sudo ldconfig /opt/rh/rh-python34/root/usr/lib64/ -v`. I've submited a PR to upstream. https://github.com/apache/qpid-proton/pull/69 I will close this issue as NOTABUG if you don't mind. *** Bug 1312586 has been marked as a duplicate of this bug. *** FYI: I've pushed Robert's fix upstream. Thanks Robert for your help with this. https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;a=commit;h=b9cd200c532e968bc349145b957c586684b08f02 -K No problem, glad to help :) I am closing this as it is fixed in upstream and there's nothing more to do. closing this is fine, but please link the mrg qpid-proton bz to track this fix getting into product It's already merged and should be part of v0.13.0 according to Jira[0]. [0]https://issues.apache.org/jira/browse/PROTON-1150 |