-
-
Notifications
You must be signed in to change notification settings - Fork 57
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
built shared objects with --library-type cdylib do not have an SONAME on musl #267
Comments
of course, the issue comes from Lines 74 to 81 in f6d4984
why on earth would this get skipped just because the target is musl (.so's should always have an soname? musl is not special here, and i assume this code doesn't get reached when building a .a in default-static), i have no idea |
Because historically musl was managed in a different way upstream. |
well, nothing changed with regards to that that i can see (discussions aside); the default -musl rustup toolchains still cannot create a cdylib on linux. this is relevant to cdylib targets only, not musl specifically. perhaps |
(cargo-c 0.9.11)
building a library (libimagequant in this case) with:
(like here)
(cdylib only needed because of #180)
then generated a library without an SONAME:
the exact same build from arch has a valid soname:
The text was updated successfully, but these errors were encountered: