-
Notifications
You must be signed in to change notification settings - Fork 31
Fix linking regression #50
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
Conversation
I don't think we want to add back a dependency on libc. Instead, we should copy the definition of |
@djc Copying the definition of |
Well, we could make it conditional on the target requiring static linking similar to the stuff that David mentioned in the issue right? We can use the current approach on macOS I think? Or do you need static linking on macOS? |
I don't see how it would be possible to statically link on macOS. I will go with the conditional approach based on the target. |
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.
Looks great, thanks for all the iterations!
|
#44 has introduced a regression that breaks building statically linked applications that depend on
resolv-conf
as explained in #49.This PR
gethostname
fromlibc
crate to solve the issue with static builds,Note that since now there is an optional dependency on
libc
, I putget_system_domain
behindsystem
feature to avoid pulling it when it's not needed.