All, The very first error encountered is "Win32 error 998" which is translated as "Invalid access to memory location". Reading the Win10 Application log I find the faulting application is perl.exe and faulting module is msys-perl5_8.dll subsequent errors fault the same file or state 'unknown'. So far I have lots of indicator messages, but I don't yet have a handle on the problem.
Prior to yesterday I have been able to compile the devel package just fine, and did so every week or so. Obviously something changed on my computer. _____________________________ Dan Malcolm CFI/II K4SHQ -----Original Message----- From: Greg Beam [mailto:ki7m...@gmail.com] Sent: Friday, March 03, 2017 5:44 PM To: WSJT software development <wsjt-devel@lists.sourceforge.net> Subject: Re: [wsjt-devel] Hamlib3 compile error Hi Dan, All, I'm not sure what's going on here either. My version of Perl, via MSYS, is 5.8.8. I was able to build Hamlib3 from MSYS directly, and JTSDK-QT via QT 5.2 and 5.5 without error. As Bill suggested, log the build and post it. To eliminate JTSDK-QT ENV, use the JTSDK-MSYS terminal, then: From JTSDK-MSYS Terminal, type the command: build-hamlib3 |tee -a hamlib3-build.log or build-hamlib3 >> hamlib3-build.log The first command allows you to watch the build progress. Then post that file to the dev list. As best I can tell, there are no versions of Perl associated with QT, so that should not be a conflict of any sort. The update process within JTSDK does not alter the MSYS installation. So, if the build worked at some point in the past, something has changed in one of the environments on your system. What, and where would be a question only you could answer. 73's Greg, KI7MT On 3/3/2017 10:58 AM, Dan Malcolm wrote: > Bill, > > Reboot didn't help and the Windows Event Log messages just reported > what was already known. I uninstalled JTSDK and then deleted the > folder. I downloaded fresh files from SourceForge, and did a complete reinstall. > The problem is not fixed. See the attached capture image. WSJT-X > compilation also failed under JTSDK-QT. There were so many error > lines that I could not scroll back far enough to see the first one. > Experience has taught me to fix the first reported failure first. Are > these problems related? > > > > _____________________________ > > Dan Malcolm CFI/II > > K4SHQ > > > > *From:*Bill Somerville [mailto:g4...@classdesign.com] > *Sent:* Thursday, March 02, 2017 10:21 AM > *To:* wsjt-devel@lists.sourceforge.net > *Subject:* Re: [wsjt-devel] Hamlib3 compile error > > > > On 02/03/2017 16:06, Dan Malcolm wrote: > > Seems the offending module is: Faulting module path: > C:\JTSDK\msys\bin\msys-perl5_8.dll. > > The problem seems to be inability to find a file > > It appears I am using Perl5_8. If memory serves, there was a > discussion about which Perl version should be used. Could 5.8 be > the problem? > > HI Dan, > > the message is telling us that the version of perl being used is the > one in the JTSDK. That should be fine. The errors were memory access > and copy errors. It could possibly be a corrupted file in the JTSDK. > If rebooting does not sort this out and there is nothing in the > Windows Event Log then it may be worth trying to re-install the JTSDK. > > 73 > Bill > G4WJS. ---------------------------------------------------------------------------- -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
