transmission fails to link with newer versions of openssl's libcrypto

[karypid]

So I was using ElCapitan and upgraded to Sierra just now. Had to reinstall ports and all.

When running port install transmission +daemon I go:

--->  Building transmission
Error: org.macports.build for port transmission returned: command execution failed
Please see the log file for port transmission for details:

Looking at the log:

:info:build ld: library not found for -lcrypto.0.9.8
:info:build clang: error: linker command failed with exit code 1 (use -v to see invocation)

I checked my openssl and it has:

$ port contents openssl | grep libcrypto
  /opt/local/lib/libcrypto.1.0.0.dylib

So this appears to need a version number change for the more recent openssl package.

Prior to upgrading to Sierra I had (this had the 0.9.8 I guess):

openssl @1.0.2d_0 (active) platform='darwin 14' archs='x86_64'

Now I have:

openssl @1.0.2j_0 (active)

Not sure at which point 0.9.8 became 1.0.0...

[karypid]

I downloaded revision 121619 and installed it successfuly with openssl 1.0.2j_0

@121619 2 years khindenburg transmission: update to 2.84 - closes #44089 (may have to rethink the …

This ssems to be something intoduced with:

@146739 8 months easieste net/transmission: update to transmission-2.92

[neverpanic (Clemens Lang)]

If you are the reporter, you don't need to Cc yourself. When reporting tickets against ports, please cc the maintainer (port info --maintainer transmission), if any.

libcrypto.0.9.8.dylib was installed by OpenSSL 0.9.8, which was provided by Apple until Sierra. While I would argue it was a bad idea to use such an old version of OpenSSL, it seems the developers of transmission probably made this choice deliberately.

I can reproduce the problem. Did you report this to the developers of transmission already?

[neverpanic (Clemens Lang)]

Upstream commits introducing this are:

• ​https://github.com/transmission/transmission/commit/1fd7c46bfacd7e61c79598763b077ba8956ef795
• ​https://github.com/transmission/transmission/commit/2bab67cb0680364f7764283002673c13c88fc109

which were not in until 2.90, so that explains why you did not see it for 2.84.

[karypid]

I was still documenting info; have not reported upstream yet.

I though it was a macports problem initially so opened a ticket here. I am not an expert, but looking at this diff: svn diff -r 121619:146739 ​https://svn.macports.org/repository/macports/trunk/dports/net/transmission

...it seems to me there is nothing changed in the port other than the version change in upstream code that could introduce this.

[karypid]

I will try to get access to upstream bug tracker and report this, referencing your finding in comment 4.

Will leave it up to the maintainer to decide what to do with this ticket. Maybe he wants to patch it, maybe not...

Thanks for your help.

[karypid]

Reported to Mac support forum upstream: ​https://forum.transmissionbt.com/viewtopic.php?f=4&t=18178 And in their bug tracker: ​https://github.com/transmission/transmission/issues/71

[stanimura]

This issue seems to have been fixed in upstream ​https://build.transmissionbt.com/job/trunk-mac/6499/changes, so that I wish it applies to the port.

[kurthindenburg (Kurt Hindenburg)]

They really just need to release 2.93 - that diff doesn't apply cleanly due to the other patches.

[ken-cunningham-webuse]

In 865fbc2ce55bca3d6acb6f5bd49469aa295493e0/macports-ports:

transmission@2.9.2 : fix missing libcrypto.0.9.8

hardlinks against libcrypto.0.9.8 which does not exist on all systems
changes to link against libcrypto
this patch will not be needed in transmission @2.9.3

closes: #52749
closes: #53743