-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
Comments
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? |
:-( |
Alternative suggestions welcome ;). |
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 |
@igortg I tried to switch the Linux build script back to using |
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. |
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
):Details about
conda
and system (conda info
):The text was updated successfully, but these errors were encountered: