-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Avoid creating empty .so/.dylib/.dll files #4468
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
Comments
This is harmless (the empty .so files just get used to track dependencies in the build system). But, I agree that the error messages you're seeing from ldconfig are confusing. We should fix this; @brson suggested using a meaningless extension for the empty files, so that we can still use them for dependencies but ldconfig won't complain about them. I'll change the title to reflect the proposed fix. |
#5217 is related |
Is it possible to replace these with symlinks? |
Fixed by 2cbfe6d. |
Compiling rust 0.5 ends up with these .so files being empty:
librusti.so
librustdoc.so
libcargo.so
librustc.so
Compilers/tools:
gcc: 4.7.2
llvm: 3.2
libffi 3.0.11
Compilation output etc:
https://gist.github.com/4524662
The text was updated successfully, but these errors were encountered: