-
Notifications
You must be signed in to change notification settings - Fork 164
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
Building on musl fails to link against libanl when not using static linking (aka MUSL_OPTIMIZED_BUILD) #1948
Comments
For libs-0.17.2 I had to rebase the patch (while finally updating our sysdig package to 0.38.0) and it looks like this:
Obviously this is not correct on glibc systems, so the patch is only applied conditionally when building on musl. Can we somehow sanitize this without breaking things? |
Hi! Thanks for opening this issue :) |
Yes, that would be one option. Like I said in the Gentoo bug mentioned above, libanl has only been an empty stub for quite some time now (since ~2021), so it's not even that critical any more. |
Opened #2036 to fix this ;) |
/milestone 0.19.0 |
/milestone 0.18.0 |
Describe the bug
sysdig can be built with
MUSL_OPTIMIZED_BUILD
- unfortunately this is misleading as it implies static linking and statically built dependencies, which is not necessary on musl.I found that using a regular build against unbundled dependencies on musl fails, as falcosecurity-libs tries to unconditionally link against
libanl
, which does not exist on musl.How to reproduce it
Build sysdig on musl with
MUSL_OPTIMIZED_BUILD
disabled and unbundled dependencies built as shared libs. It should error out with a failure to link-lanl
.Expected behaviour
sysdig should build successfully on musl against shared unbundled dependencies.
Environment
musl 1.2.5 in a Gentoo chroot (with musl as system C library)
Installation method: from source - I am the package maintainer :)
Additional information
We had to fix this in Gentoo for an older version in this commit:
https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=844fbd1e96beda0fb94ea06aba8f2618bfdad1f7
The text was updated successfully, but these errors were encountered: