-
Notifications
You must be signed in to change notification settings - Fork 567
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
build: Fix musl warnings #5431
build: Fix musl warnings #5431
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code looks okay. Alas I've got no way to test this properly.
The For testing I just use an podman container. $ podman run --rm -it alpine:latest
# apk update
# apk add git build-base gawk linux-headers
# git clone --depth=1 https://github.com/netblue30/firejail.git
# cd firejail
# git fetch origin pull/5431/head:pr-5431
# git switch pr-5431
# ./configure --enable-fatal-warnings [--enable-analyzer]
# make -j4
libtrace(log) redefinition of '...'
Running with
|
Thanks! I'll have a closer look at it. |
60a3405
to
1e0d4c1
Compare
The non-null warning looks like a false-positive to me:
Even if strdup returns NULL, I don't see how NULL could get passed to strlen, as it would have exited... |
1e0d4c1
to
a86c4fe
Compare
in musl they are just redefines of the non-64 versions
@rusty-snake I just checked with an alpine:edge container, which has gcc-12. |
Fixes two warnings when building firejail with musl libc.
Should fix #5421.