[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [EXTERNAL] Re: Libssh on Windows 10
[Thread Prev] | [Thread Next]
[Date Prev] | [Date Next]
- Subject: RE: [EXTERNAL] Re: Libssh on Windows 10
- From: "Kennedy, Marcus A." <Marcus.Kennedy@xxxxxxxxxx>
- Reply-to: libssh@xxxxxxxxxx
- Date: Mon, 30 Sep 2019 22:07:51 +0000
- To: "libssh@xxxxxxxxxx" <libssh@xxxxxxxxxx>
Humph. I didn't know there was a 1.1.1 ;). Didn't occur to me to look for a new version as this configuration worked with Windows 7. So, thanks for the info. I'm building it up right now. Andy From: Franciszek Juras <franciszekjuras@xxxxxxxxx> Sent: Monday, September 30, 2019 4:55 PM To: libssh@xxxxxxxxxx Subject: [EXTERNAL] Re: Libssh on Windows 10 AFAIK libssh 0.9 should be build against openssl 1.1.1 And openssl 1.0.2 support ends at the end of the year anyway. FJ pon., 30 wrz 2019, 23:41 użytkownik Kennedy, Marcus A. <Marcus.Kennedy@xxxxxxxxxx<mailto:Marcus.Kennedy@xxxxxxxxxx>> napisał: All, libssh-0.9.0 openssl-1.0.2s I'm just now digging into this, but I'm getting a "Debug Assertion Failed". Attaching to it with VS 2017 debugger showed me to be in a call to SAFE_FREE() deep within a pki_ function. While discussing it with someone on my team, it occurred to me that I had built both openssl and libssh using a Windows 7 SDK. I rebuilt just a bit ago and am still getting the same results. Both libssh and openssl were built using the VS2017 SDK. The previous version I obviously built in Debug mode (as I could step deep into the library, but now I cannot -- no idea why, I used the same set of instructions I wrote the first time through the build). Anyone have an idea where I could begin to trace this down? Thanks, Andy
Archive administrator: postmaster@lists.cynapses.org