[GH-ISSUE #2046] Unable to build without linking against libssl/libcrypt #861

New issue

Closed

opened 2026-03-16 00:37:42 +03:00 by kerem · 2 comments

kerem commented

2026-03-16 00:37:42 +03:00

Owner

Originally created by @cbgbt on GitHub (Oct 4, 2023).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/2046

Describe the bug
Even with a minimal set of features enabled, binaries still link against libssl and libcrypt.

To Reproduce
Steps to reproduce the behavior:

$ cargo build --no-default-features --features 'resolver,sqlite'

This fails to build if openssl lib/headers aren't installed, and produces a binary that dynamically links against them if they are.

Expected behavior
I anticipated that this would successfully build on a system without openssl dynamic libraries and headers.

Version:
Version: 0.23.0

Additional context
I believe, though haven't confirmed, that this is due to unconditional openssl dependencies in the workspace root (e.g.).

I'm happy to look into conditionalizing this, I just wasn't sure if I was missing something.

Originally created by @cbgbt on GitHub (Oct 4, 2023). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/2046 **Describe the bug** Even with a minimal set of features enabled, binaries still link against `libssl` and `libcrypt`. **To Reproduce** Steps to reproduce the behavior: ```bash $ cargo build --no-default-features --features 'resolver,sqlite' ``` This fails to build if openssl lib/headers aren't installed, and produces a binary that dynamically links against them if they are. **Expected behavior** I anticipated that this would successfully build on a system without openssl dynamic libraries and headers. **Version:** Version: 0.23.0 **Additional context** I believe, though haven't confirmed, that this is due to unconditional openssl dependencies in the workspace root ([e.g.](https://github.com/bluejekyll/trust-dns/blob/ee530bf7496f75e83d368a102502cd902d618ee6/Cargo.toml#L60)). I'm happy to look into conditionalizing this, I just wasn't sure if I was missing something.

kerem closed this issue

2026-03-16 00:37:48 +03:00

kerem commented

2026-03-16 00:37:54 +03:00

Author

Owner

@cbgbt commented on GitHub (Oct 4, 2023):

I went to take a look at this and realized that it's actually not true of the main branch. I haven't worked out why that is yet, but this issue isn't necessary. Thanks!

@cbgbt commented on GitHub (Oct 4, 2023): I went to take a look at this and realized that it's actually not true of the `main` branch. I haven't worked out why that is yet, but this issue isn't necessary. Thanks!

kerem commented

2026-03-16 00:37:59 +03:00

Author

Owner

@djc commented on GitHub (Oct 4, 2023):

This is building the binary? There may be some incorrect dependency edges that got cleaned up in #2028.

@djc commented on GitHub (Oct 4, 2023): This is building the binary? There may be some incorrect dependency edges that got cleaned up in #2028.

kerem referenced this issue

2026-03-16 02:23:18 +03:00

[PR #861] [CLOSED] Bump ring from 0.16.7 to 0.16.9 #1749