Skip to content
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

Transmission hardcoded to link against libcrypto 0.9.8 makes build not work with newer openssl #71

Closed
karypid opened this issue Oct 30, 2016 · 2 comments
Milestone

Comments

@karypid
Copy link

karypid commented Oct 30, 2016

This is a follow-up issue, discussed on the forum in: https://forum.transmissionbt.com/viewtopic.php?f=4&t=18178

Transmission's build files seem to have hard-codded the use of libcrypto 0.9.8 som time around version 2.90. As a result, when bulding, it fails to link on newer versions of macports. This is discussed in https://trac.macports.org/ticket/52749#comment:4

Older versions (specifically 2.84) compile and work fine even with the latest version of openssl. Could you please review and hopefully undo the commits discussed in the comment linked above in macports? It seems like the version was pinned intentionally, but this does not seem to be the best option anymore.

@favadi
Copy link

favadi commented Nov 27, 2016

We should restore the ability to build with newer versions openssl as it usually takes Apple some time to patch the builtin version.

@mikedld mikedld added the bug label Jan 13, 2017
@mikedld
Copy link
Member

mikedld commented Jan 18, 2017

FYI, I've committed CMake files for Mac client recently. Using CMake instead of xcodebuild should resolve the issue as well.

@mikedld mikedld modified the milestone: 3.00 Jul 4, 2017
@mikedld mikedld modified the milestones: 3.00, 2.93 Jan 16, 2018
mikedld added a commit that referenced this issue Jan 16, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants