Bug 1312586

Rodolfo, sending this one your way. Not sure if it belongs with the SCL team.

I can reproduce the problem:

----------------------------------------------------------------
$ docker run --rm -it --user root openshift/python-33-centos7 bash
bash-4.2# pip install python-qpid-proton
Downloading/unpacking python-qpid-proton
  Downloading python-qpid-proton-0.12.0.tar.gz (157kB): 157kB downloaded
  Running setup.py (path:/tmp/pip_build_root/python-qpid-proton/setup.py) egg_info for package python-qpid-proton
    
Installing collected packages: python-qpid-proton
  Running setup.py install for python-qpid-proton
    Did not find libqpid-proton via pkg-config:
    Bundling qpid-proton into the extension
    fetching http://www.apache.org/dist/qpid/proton/0.12.0/qpid-proton-0.12.0.tar.gz into build/bundled
    /opt/rh/python33/root/usr/bin/python3: error while loading shared libraries: libpython3.3m.so.1.0: cannot open shared object file: No such file or directory
    /opt/rh/python33/root/usr/bin/python3: error while loading shared libraries: libpython3.3m.so.1.0: cannot open shared object file: No such file or directory
    Using openssl (found via pkg-config).
...
/tmp/pip_build_root/python-qpid-proton/build/bundled/qpid-proton/proton-c/src/codec/decoder.c: In function 'pni_decoder_decode_type':

/tmp/pip_build_root/python-qpid-proton/build/bundled/qpid-proton/proton-c/src/codec/decoder.c:451:15: error: 'PNE_DESCRIPTOR' undeclared (first use in this function)

   if (next == PNE_DESCRIPTOR) {

               ^

error: command 'gcc' failed with exit status 1
----------------------------------------------------------------





However, it turns out that `cyrus-sasl-devel` is already installed:

----------------------------------------------------------------
bash-4.2# yum info cyrus-sasl-devel
Installed Packages
Name        : cyrus-sasl-devel
Arch        : x86_64
Version     : 2.1.26
Release     : 19.2.el7
Size        : 1.0 M
Repo        : installed
From repo   : base
Summary     : Files needed for developing applications with Cyrus SASL
URL         : http://asg.web.cmu.edu/sasl/sasl-library.html
License     : BSD with advertising
Description : The cyrus-sasl-devel package contains files needed for developing and
            : compiling applications which use the Cyrus SASL library.
----------------------------------------------------------------


I tried:

- yum update cyrus-sasl-devel
- pip install -U pip (update pip)
- yum install saslwrapper-devel
- yum install qpid-proton-c-devel

But none of the steps above helped.



Finally, I tried Python 2.7:

----------------------------------------------------------------
$ docker run --rm -it --user root centos/python-27-centos7 bash
bash-4.2# pip install python-qpid-proton
Downloading/unpacking python-qpid-proton
  Downloading python-qpid-proton-0.12.0.tar.gz (157kB): 157kB downloaded
  Running setup.py (path:/tmp/pip-build-jsbbFO/python-qpid-proton/setup.py) egg_info for package python-qpid-proton
    
Installing collected packages: python-qpid-proton
  Running setup.py install for python-qpid-proton
    Did not find libqpid-proton via pkg-config:
    Bundling qpid-proton into the extension
    fetching http://www.apache.org/dist/qpid/proton/0.12.0/qpid-proton-0.12.0.tar.gz into build/bundled
    Using openssl (found via pkg-config).
...
    
Successfully installed python-qpid-proton
Cleaning up...
----------------------------------------------------------------


And then Python 3.4:

----------------------------------------------------------------
$ docker run --rm -it --user root centos/python-34-centos7 bash
bash-4.2# pip install python-qpid-proton
Downloading/unpacking python-qpid-proton
  Downloading python-qpid-proton-0.12.0.tar.gz (157kB): 157kB downloaded
  Running setup.py (path:/tmp/pip-build-vo35namb/python-qpid-proton/setup.py) egg_info for package python-qpid-proton
    
Installing collected packages: python-qpid-proton
  Running setup.py install for python-qpid-proton
    Did not find libqpid-proton via pkg-config:
    Bundling qpid-proton into the extension
    fetching http://www.apache.org/dist/qpid/proton/0.12.0/qpid-proton-0.12.0.tar.gz into build/bundled
    /opt/rh/rh-python34/root/usr/bin/python3: error while loading shared libraries: libpython3.4m.so.rh-python34-1.0: cannot open shared object file: No such file or directo
ry
    /opt/rh/rh-python34/root/usr/bin/python3: error while loading shared libraries: libpython3.4m.so.rh-python34-1.0: cannot open shared object file: No such file or directo
ry
    Using openssl (found via pkg-config).
...
/tmp/pip-build-vo35namb/python-qpid-proton/build/bundled/qpid-proton/proton-c/src/codec/decoder.c:451:15: error: 'PNE_DESCRIPTOR' undeclared (first use in this function)

   if (next == PNE_DESCRIPTOR) {

               ^

error: command 'gcc' failed with exit status 1
----------------------------------------------------------------



According to PyPI python-qpid-proton supports Python 3.3:

https://pypi.python.org/pypi/python-qpid-proton/0.12.0


So I don't know why it installs out-of-the-box for Python 2.7 and not for Python 3.3, since in both cases it is using Python from SCL.


*******************************************
But I did notice that for both Python 3.3 and 3.4 there's an error message:

    /opt/rh/python33/root/usr/bin/python3: error while loading shared libraries: libpython3.3m.so.1.0: cannot open shared object file: No such file or directory
    /opt/rh/rh-python34/root/usr/bin/python3: error while loading shared libraries: libpython3.4m.so.rh-python34-1.0: cannot open shared object file: No such file or directory
*******************************************

@hhorak, do you know if there's something about the Python versions that could be causing this problem?
Why do we get the errors above for Python 3.3 and 3.4 and not for 2.7?

(In reply to Rodolfo Carvalho from comment #2)
> But I did notice that for both Python 3.3 and 3.4 there's an error message:
> 
>     /opt/rh/python33/root/usr/bin/python3: error while loading shared
> libraries: libpython3.3m.so.1.0: cannot open shared object file: No such
> file or directory
>     /opt/rh/rh-python34/root/usr/bin/python3: error while loading shared
> libraries: libpython3.4m.so.rh-python34-1.0: cannot open shared object file:
> No such file or directory
> *******************************************
> 
> @hhorak, do you know if there's something about the Python versions that
> could be causing this problem?
> Why do we get the errors above for Python 3.3 and 3.4 and not for 2.7?

I don't know what is the difference between 2.7 and 3.3/3.4, but the error above seems like problem with SCL environment, that it is not properly set. Can you check the environment at the time the error above occurs?

@hhorak sure, here it goes:

----------------------------------------------------------------
$ docker run --rm -it --user root centos/python-27-centos7 bash
bash-4.2# printenv
MANPATH=/opt/rh/python27/root/usr/share/man:
HOSTNAME=2659ef617d21
TERM=xterm
X_SCLS=python27 
LD_LIBRARY_PATH=/opt/rh/python27/root/usr/lib64
PYTHON_VERSION=2.7
PATH=/opt/rh/python27/root/usr/bin:/opt/app-root/src/.local/bin/:/opt/app-root/src/bin:/opt/app-root/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
STI_SCRIPTS_URL=image:///usr/libexec/s2i
PWD=/opt/app-root/src
STI_SCRIPTS_PATH=/usr/libexec/s2i
HOME=/opt/app-root/src
SHLVL=1
XDG_DATA_DIRS=/opt/rh/python27/root/usr/share
PKG_CONFIG_PATH=/opt/rh/python27/root/usr/lib64/pkgconfig
_=/usr/bin/printenv
bash-4.2# ls /opt/rh/python27/root/usr/lib64
X11  games  libpython2.7.so  libpython2.7.so.1.0  pkgconfig  pm-utils  python2.7  sse2  tls
bash-4.2# ls /opt/rh/python27/root/usr/lib64 -l
total 1800
dr-xr-xr-x.  2 root root       6 Oct  1 15:50 X11
dr-xr-xr-x.  2 root root       6 Oct  1 15:50 games
lrwxrwxrwx.  1 root root      19 Feb 11 16:53 libpython2.7.so -> libpython2.7.so.1.0
-r-xr-xr-x.  1 root root 1802616 Oct  1 16:25 libpython2.7.so.1.0
drwxr-xr-x.  2 root root      62 Feb 11 16:53 pkgconfig
dr-xr-xr-x.  5 root root      52 Feb 11 16:52 pm-utils
drwxr-xr-x. 26 root root   20480 Feb 11 16:52 python2.7
dr-xr-xr-x.  2 root root       6 Oct  1 15:50 sse2
dr-xr-xr-x.  2 root root       6 Oct  1 15:50 tls
----------------------------------------------------------------

----------------------------------------------------------------
$ docker run --rm -it --user root openshift/python-33-centos7 bash
bash-4.2# printenv
MANPATH=/opt/rh/python33/root/usr/share/man:
HOSTNAME=c6823c812853
TERM=xterm
X_SCLS=python33 
LD_LIBRARY_PATH=/opt/rh/python33/root/usr/lib64
PYTHON_VERSION=3.3
PATH=/opt/rh/python33/root/usr/bin:/opt/app-root/src/.local/bin/:/opt/app-root/src/bin:/opt/app-root/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
STI_SCRIPTS_URL=image:///usr/libexec/s2i
PWD=/opt/app-root/src
STI_SCRIPTS_PATH=/usr/libexec/s2i
HOME=/opt/app-root/src
SHLVL=1
XDG_DATA_DIRS=/opt/rh/python33/root/usr/share
PKG_CONFIG_PATH=/opt/rh/python33/root/usr/lib64/pkgconfig
_=/usr/bin/printenv
bash-4.2# ls /opt/rh/python33/root/usr/lib64
X11  games  libpython3.3m.so  libpython3.3m.so.1.0  libpython3.so  pkgconfig  pm-utils  python3.3  sse2  tls
bash-4.2# ls /opt/rh/python33/root/usr/lib64 -l
total 2468
dr-xr-xr-x.  2 root root       6 Oct  1 16:32 X11
dr-xr-xr-x.  2 root root       6 Oct  1 16:32 games
lrwxrwxrwx.  1 root root      20 Feb 11 16:59 libpython3.3m.so -> libpython3.3m.so.1.0
-rwxr-xr-x.  1 root root 2503984 Oct  1 17:02 libpython3.3m.so.1.0
-rwxr-xr-x.  1 root root    6688 Oct  1 17:02 libpython3.so
drwxr-xr-x.  2 root root      84 Feb 11 16:59 pkgconfig
dr-xr-xr-x.  5 root root      52 Feb 11 16:59 pm-utils
drwxr-xr-x. 32 root root    8192 Feb 11 16:59 python3.3
dr-xr-xr-x.  2 root root       6 Oct  1 16:32 sse2
dr-xr-xr-x.  2 root root       6 Oct  1 16:32 tls
----------------------------------------------------------------

I don't really have an idea, moving needinfo to the Python maintainer. Robert, do you have an idea what might be different here?

This is actually a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1312590 , I've already sent a PR to qpid-proton to address the issue.

*** This bug has been marked as a duplicate of bug 1312590 ***

Btw, it worked with python27 because system python is linked against same .so file as python shipped within python27 collection, so python27 collection used the one located in /usr/lib64 (instead of /opt/rh/..../usr/lib64/).

Thanks Robert!