+yuri > On Feb 24, 2020, at 15:50, Chris Ross <[email protected]> wrote: >> >> ps, looking at the noted https://github.com/arvidn/libtorrent/issues/4204 >> something was merged on Jan 7 that someone reported fixing this issue for >> FreeBSD. > > > Okay. So, looking at the sources and the aforementioned "fix": That commit > that fixes it for FreeBSD was merged into lib torrent-rasterbar, and should > be available in version 1.2.4. Also, I applied the diff by hand to my > sources of py-libtorrent-rasterber11 in the ports tree, and was able to get > it to install the shared library properly. I'm guessing the 1.1.10 version > didn't have that problem, but 1.1.14 and 1.2 did. Or, I did something > similar to the 1.1.10_5 version of py-libtorrent-rasterbar in my tree and > failed to keep track of it. > > So, if deluge 2.0.x works with libtorrent-rasterbar 1.2 there's a clear path > forward. If it works with 1.1.x and not 1.2.x, it's more complicated. Let > me know how you can proceed after trying libtorrent-rasterbar 1.2.4.
It looks like there are a few changes in libtorrent 1.2, https://www.libtorrent.org/upgrade_to_1.2-ref.html I notice that net-p2p/libtorrent-rasterbar has already been updated to 1.2.4. I think this means that the python module would work now if similarly updated. Also, I notice that according to the 1.2 release notes, boost has been replaced by std, but both libtorrent-rasterbar and py-libtorrent-rasterbar still seem to require boost. Is this an oversight, or am I misreading https://www.libtorrent.org/upgrade_to_1.2-ref.html ? Thanks! - Chris _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[email protected]"
