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
--strip should emit no debug info and result in a stripped binary according to binutils #351
Comments
Postponing to 0.3.0. We only have to solve this issue in the self-hosted compiler. |
Strip now works fairly well but it does not strip everything. It's no longer a bug. |
This bit me just now when packaging my project for Debian. Namely, the last stage (linting) of $ zig build-lib --name foo -target x86_64-linux-gnu -dynamic --strip
$ file libfoo.so.0.0.0
libfoo.so.0.0.0: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, not stripped
$ strip libfoo.so.0.0.0
$ file libfoo.so.0.0.0
libfoo.so.0.0.0: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, stripped The Lintian error is unstripped-binary-or-object:
This will affect all shared libraries produced by Zig when packaged for Debian or Ubuntu. The workaround for now is to either add an explicit spurious |
This appears to be fixed.
0.10.0-dev.2562+61844b6bd |
Fixed by 366c767 |
--strip
is supposed to not emit debug info, but it still does.Additionally if you use
file
on the binary it should say "stripped" and it should not say "not stripped".The text was updated successfully, but these errors were encountered: