mirror of
https://github.com/mumble-voip/mumble.git
synced 2026-03-03 00:46:56 -05:00
Compilation error with security/OpenSSL (OpenSSL 1.1.1i 8 Dec 2020) #2119
Labels
No labels
GlobalShortcuts
Hacktoberfest
accessibility
acl
asio
audio
bonjour
bsd
bug
build
certificate
ci
client
code
documentation
external-bug
feature-request
gRPC
github
good first issue
help wanted
help-needed
ice
installer
linux
macOS
needs-ckeck-with-latest-version
needs-more-input
overlay
positional audio
priority/P0 - Blocker
priority/P1 - Critical
priority/P2 - Important
priority/P3 - Somewhat important
priority/P4 - Low
public-server-registration
qt
recording
release-management
server
stale-no-response
stale-support
support
task
test
theme
translation
triage
ui
windows
wontfix
x64
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/mumble-mumble-voip#2119
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 @gessel on GitHub (Feb 15, 2021).
Describe the bug
Build process errors out trying to locate libcrypto.so.11
Steps to Reproduce
portmaster -d audio/murmur
Desktop (please complete the following information):
(server side)
FreeBSD 11.3-RELEASE-p8 #0 r360490
murmur 1.3.3_1 (mumble-voip-mumble-1.3.3_GH0.tar.gz)
Additional context
Note I ran into a LibreSSL bug #4725 and so switched a jail to OpenSSL from ports (not base) and tried building murmur there:
Note other ports depending on OpenSSL build normally (and work as expected):
Build terminates with:
It appears the port is correctly parsing the make.conf directive to use OpenSSL from ports:
Ice 3.6.4, built as a dependency for murmur, apparently finds the SSL libraries:
Any hints?
@davidebeatrici commented on GitHub (Feb 15, 2021):
Mumble is linking to
libcrypto.so.8instead oflibcrypto.so.11.Is removing the older library an option?
@Krzmbrzl commented on GitHub (Feb 16, 2021):
As a test you could also try to disable Ice to see if it is working then. In order to do so, use
-Dice=OFFwhen invoking cmake@gessel commented on GitHub (Feb 16, 2021):
Indeed, that changes the error but compilation still did not succeed. In FreeBSD land:
which yielded:
I'll try reverting to base SSL (OpenSSL 1.0.2s-freebsd 28 May 2019) rather than the current security/openssl from ports (OpenSSL 1.1.1i 8 Dec 2020). It will take some time to rebuild everything...
@Krzmbrzl commented on GitHub (Feb 16, 2021):
I think we at some point received a report that some newer OpenSSL version changed some function names and was thus incompatible with our current implementation. This could've been 1.1 🤔
@gessel commented on GitHub (Feb 16, 2021):
hmm... this could be a problem. Base is 1.0.2s, but:
So I removed that port (and some other cruft) with # portmaster -e net/qt5-network, and I'll see where I get to...
@stale[bot] commented on GitHub (Feb 21, 2021):
This support-issue has been automatically marked as stale because it has not had recent activity. If no further activity occurs, the issue will be automatically closed as we'll assume your problem to be fixed.
@gessel commented on GitHub (Jun 6, 2021):
OpenSSL is up to openssl-1.1.1k_1,1
But still no love.
Based on googling around, I suspect linking is confused by base SSL:
and this bit of potential confusion:
@davidebeatrici commented on GitHub (Jun 6, 2021):
This may be caused by Qt being linked to a different OpenSSL version.
@gessel commented on GitHub (Jun 6, 2021):
Possibly, but the entire system and all ports (
portmaster -afdin host, rebuild basejail, then rebuild jails) was done. I'll check withlddand report back.