Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

0.2 package does not create libyaml-0.so.2 so link #13

Closed
igortg opened this issue Dec 2, 2019 · 6 comments · Fixed by #14
Closed

0.2 package does not create libyaml-0.so.2 so link #13

igortg opened this issue Dec 2, 2019 · 6 comments · Fixed by #14

Comments

@igortg
Copy link

igortg commented Dec 2, 2019

Issue:

The 0.2.2 version of yaml package does not create a symbolic link for libyaml-0.so.2 (as the version 0.1.7 does). So some of dependents are not working with the latest version of yaml.

From what I checked, latest uwsgi package and some old version of pyyaml are throwing the following error: error while loading shared libraries: libyaml-0.so.2: cannot open shared object file: No such file or directory

By checking the yaml package from other providers, it seems that libyaml-0.so.2 should be there:


Environment (conda list):
$ conda list
# Name                    Version                   Build  Channel
_libgcc_mutex             0.1                        main    conda-forge
ca-certificates           2019.11.28           hecc5488_0    conda-forge
certifi                   2019.11.28               py36_0    conda-forge
icu                       64.2                 he1b5a44_1    conda-forge
jansson                   2.11              h516909a_1001    conda-forge
libffi                    3.2.1             he1b5a44_1006    conda-forge
libgcc-ng                 9.2.0                hdf63c60_0    conda-forge
libiconv                  1.15              h516909a_1005    conda-forge
libstdcxx-ng              9.2.0                hdf63c60_0    conda-forge
libxml2                   2.9.10               hee79883_0    conda-forge
ncurses                   6.1               hf484d3e_1002    conda-forge
openssl                   1.0.2t               h14c3975_0    conda-forge
pcre                      8.43                 he1b5a44_0    conda-forge
pip                       19.3.1                   py36_0    conda-forge
python                    3.6.7             hd21baee_1002    conda-forge
readline                  7.0               hf8c457e_1001    conda-forge
setuptools                42.0.2                   py36_0    conda-forge
sqlite                    3.28.0               h8b20d00_0    conda-forge
tk                        8.6.10               hed695b0_0    conda-forge
uwsgi                     2.0.17.1         py36h2184488_1    conda-forge
wheel                     0.33.6                   py36_0    conda-forge
xz                        5.2.4             h14c3975_1001    conda-forge
yaml                      0.2.2                he1b5a44_0    conda-forge
zlib                      1.2.11            h516909a_1006    conda-forge

Details about conda and system ( conda info ):
$ conda info

     active environment : yaml-test
    active env location : /opt/conda/envs/yaml-test
            shell level : 2
       user config file : /root/.condarc
 populated config files : /root/.condarc
          conda version : 4.6.14
    conda-build version : not installed
         python version : 3.7.3.final.0
       base environment : /opt/conda  (writable)
           channel URLs : https://conda.anaconda.org/conda-forge/linux-64
                          https://conda.anaconda.org/conda-forge/noarch
                          https://repo.anaconda.com/pkgs/main/linux-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/free/linux-64
                          https://repo.anaconda.com/pkgs/free/noarch
                          https://repo.anaconda.com/pkgs/r/linux-64
                          https://repo.anaconda.com/pkgs/r/noarch
          package cache : /opt/conda/pkgs
                          /root/.conda/pkgs
       envs directories : /opt/conda/envs
                          /root/.conda/envs
               platform : linux-64
             user-agent : conda/4.6.14 requests/2.21.0 CPython/3.7.3 Linux/4.15.0-70-generic debian/9 glibc/2.24
                UID:GID : 0:0
             netrc file : None
           offline mode : False


@mbargull
Copy link
Member

mbargull commented Dec 2, 2019

xref: yaml/libyaml#141

Both Arch and Alpine do not use the CMake build:

@seanyen, unless you know how to convince the CMake build to create the symlinks, can you switch this back to the Autotools build?

@ocefpaf
Copy link
Member

ocefpaf commented Dec 2, 2019

@seanyen, unless you know how to convince the CMake build to create the symlinks, can you switch this back to the Autotools build?

:-(

@mbargull
Copy link
Member

mbargull commented Dec 2, 2019

:-(

Alternative suggestions welcome ;).
(I have too little in-depth knowledge of either build tool to know what the best thing to do is here. Both tools confuse me. At some point I really have to dig into those, I guess; but currently I just can't afford to do that :/ ...)

@ocefpaf
Copy link
Member

ocefpaf commented Dec 2, 2019

My frowning face was directed to cmake not your suggestions. I'm happy using it only on Windows so we can have better symlinks support and avoid conda-forge/uwsgi-feedstock#32

@seanyen
Copy link
Contributor

seanyen commented Dec 2, 2019

@igortg I tried to switch the Linux build script back to using Autotools. Let me know if it fixes the non-Windows builds linkage issues.

@mbargull
Copy link
Member

mbargull commented Dec 2, 2019

ls -lA lib/*.so*
lrwxrwxrwx 1 conda conda     18 Dec  2 20:26 lib/libyaml-0.so.2 -> libyaml-0.so.2.0.6
-rwxrwxr-x 1 conda conda 125064 Dec  2 20:26 lib/libyaml-0.so.2.0.6
lrwxrwxrwx 1 conda conda     18 Dec  2 20:26 lib/libyaml.so -> libyaml-0.so.2.0.6

Success! Thanks @seanyen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants