mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 03:05:51 +03:00
[GH-ISSUE #39] Build fails with rust 1.12.0-beta.1 #327
Labels
No labels
blocked
breaking-change
bug
bug:critical
bug:tests
cleanup
compliance
compliance
compliance
crate:all
crate:client
crate:native-tls
crate:proto
crate:recursor
crate:resolver
crate:resolver
crate:rustls
crate:server
crate:util
dependencies
docs
duplicate
easy
easy
enhance
enhance
enhance
feature:dns-over-https
feature:dns-over-quic
feature:dns-over-tls
feature:dnsssec
feature:global_lb
feature:mdns
feature:tsig
features:edns
has workaround
ops
perf
platform:WASM
platform:android
platform:fuchsia
platform:linux
platform:macos
platform:windows
pull-request
question
test
tools
tools
trust
unclear
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hickory-dns#327
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @19h on GitHub (Aug 22, 2016).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/39
Hey,
Since I'm using a macOS beta (Sierra) on my computer, I'm forced to use 1.12.0-beta1.
The build fails with rust 1.12.0:
Edit:
Seems like
CRYPTO_LOCK_SSLwas removed from openssl. Seems to be an upstream issue with the openssl crate..?@bluejekyll commented on GitHub (Aug 22, 2016):
Quite possible. I haven't tried 1.12.0. What version of OpenSSL do you have installed? I personally install the one in brew, rather than using Apple's fork.
@19h commented on GitHub (Aug 22, 2016):
OpenSSL 1.1.0-pre4 (beta) 16 Mar 2016through brew. How do you force rust to use the Homebrew libraries?@bluejekyll commented on GitHub (Aug 22, 2016):
These are the instructions I have in the README.md at the root (please let me know if they are not accurate):
That
brew link --force opensslwill cause the version brew installs to be the one that most of your dev tools will choose to use. I don't think it affects Apple's tools (though if this matters to you, you should double check it).@19h commented on GitHub (Aug 22, 2016):
Homebrew just recently started refusing to do "--force":
Can I somehow pass this to rust?
@19h commented on GitHub (Aug 22, 2016):
Okay this is ugly. I got around the "endogenous" rust build error by adding this to
~/.cargo/config:Then the C-shim failed. Got around that by adding
CFLAGS="-I/usr/local/opt/openssl/include -L/usr/local/opt/openssl/lib".Now
openssl-sysis failing, because it seems like Rust / Cargo / et al. is not honoring CXXFLAGS (though it honors CFLAGS):@bluejekyll commented on GitHub (Aug 22, 2016):
Have you tried these instructions from the OpenSSL project:
@19h commented on GitHub (Aug 22, 2016):
Holy moly, that worked.
So, summing it up:
Add to cargo config:Prior to build:
cargo build💰🍻
@bluejekyll commented on GitHub (Aug 22, 2016):
Is 1) actually necessary?
@19h commented on GitHub (Aug 22, 2016):
Let me check.. no.
@19h commented on GitHub (Aug 31, 2016):
Thanks! 🐎 🍻