Changes between Initial Version and Version 1 of Ticket #3201, comment 44


Ignore:
Timestamp:
Nov 14, 2019 12:33:40 AM (11 months ago)
Author:
mhertz
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #3201, comment 44

    initial v1  
    1 Since Cas's install instructions in this thread results in not being able to announce to https trackers, then i'm trying to build libtorrent v1.1.13 qith openssl, but even without openssl, then it doesn't work right in deluge2 for me, even though I can import it fine in a python ierminal still outside of deluge2. I can build latest libtorrent v1.2.2 and run in deluge2 fine, but just not v1.1.13, and don't get it. 
     1Since Cas's install instructions in this thread results in not being able to announce to https trackers, then i'm trying to build libtorrent v1.1.13 with openssl, but even without openssl, then it doesn't work right in deluge2 for me, even though I can import it fine in a python terminal still outside of deluge2. I can build latest libtorrent v1.2.2 and run in deluge2 fine, but just not v1.1.13, and don't get it. 
    22 
    3 The strange thing also, is that often then right after building it, then when adding it to deluge2 and firering it up, then deluge2 start fine with it, but then if disconnecting from daemon and closing deluge2 and starting it again, then it never works regardless of how many times trying. Is shows an error 10061 of connection actively refused by destination computer, and loading it into dependency walker and profiling it(deluged.exe), shows this error: 
     3The strange thing also, is that often then right after building it, then when adding it to deluge2 and firering it up, then deluge2 start fine with it, but then if disconnecting from daemon and closing deluge2 and starting it again, then it never works regardless of how many times trying. It shows an error 10061 of connection actively refused by destination computer, and loading it into dependency walker and profiling it(deluged.exe), shows this error: 
    44{{{ 
    55Second chance exception 0xE06D7363 (Microsoft C++ Exception) occurred in "KERNELBASE.DLL" at address 0x00007FFB59ED50D8. 
     
    191900:59:08 [DEBUG   ][deluge.ui.gtk3.connectionmanager  :319 ] Failed to connect: Connection was refused by other side: 10061: Der kunne ikke oprettes forbindelse, fordi destinationscomputeren aktivt nægtede det.. 
    2020}}} 
    21 (The danish part means that there couldn't be made a connection because destination computer actively refused it) 
     21(The danish part means that there couldn't be made a connection because destination computer actively refused it - I also just in case tried disabling firewall, but didn't help either) 
    2222 
    23 I have tried 5 different boost versions, where most give linking errors, which either is online reported to be unresolved or fixed by changing boost version. I know using boost over v1.66 needs a patch added to jamfile to support python3, but I do add that also, which makes it run, but fails later with linking errors. I usually stick to v1.66 because was reported by a libtorrent dev to be recommended as didn't need patches, and using that, makes it be imported every time in a terminal, but just not in deluge2, except often right after the building. I always include runtime files needed, and also used b2 option of static runtime linking without any change. 
     23I have tried 5 different boost versions, where most give linking errors, which either is online reported to be unresolved or fixed by changing boost version. I know using boost over v1.66 needs a patch added to jamfile to support python3 or something along those lines, but I do add that also, which makes it run, but fails later with linking errors. I usually stick to v1.66 because was reported by a libtorrent dev to be recommended as didn't need patches, and using that, makes it be imported every time in a terminal, but just not in deluge2, except often right after the building. I always include runtime files needed, and also tried b2 option of static runtime linking, but again without any change. 
    2424 
    25 I use python v3.68, and msvc build tools latest version(14.23 = 2019), but have tried also v14.16 = 2017), and change setup.py to reflect the proper msvc version, which is added to b2 command-line then, and address-model=64 or whatever it is called I also use, and again, I build libtorrent v1.2.2 with openssl fine, and doesn't have this issue and always connects, but it does however still show a connection error or two of the one posted above, but always connects fine anyway, as 5 or 6 of those is supported before failing I can see. 
     25I use python v3.68, and msvc-build-tools latest version 2019(14.23), but have tried also 2017 edition(v14.16), and change setup.py to reflect the proper msvc version, which is added to b2 command-line then, and address-model=64 I also use, and again, I build libtorrent v1.2.2 with openssl fine, and doesn't have this issue and always connects in deluge2, but it does however still show a connection error or two of the one posted above, but always connects fine anyway, as 5 or 6 of those is supported before failing I can see. 
    2626 
    27 Thanks alot in advance, as this is driving me freakin' crazy soon, as have run 100 test of this now I'd guess. 
     27Thanks alot in advance, as this is driving me freakin' crazy soon, as have run 100 test of this now I'd guess, in the last weeks time or so.