Bill,
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?
_____________________________
Dan Malcolm CFI/II
K4SHQ
From: Bill Somerville [mailto:g4...@classdesign.com]
Sent: Thursday, March 02, 2017 9:19 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Hamlib3 compile error
On 02/03/2017 14:55, Dan Malcolm wrote:
Just tried to recompile Hamlib3 using JTSDK-MSYS and this is the result:
CDPATH="${ZSH_VERSION+.}:" && cd ../src && /bin/sh
/c/JTSDK/src/hamlib3/src/build-aux/missing --run aclocal-1.12 -I macros
--install
0 [main] perl 18760 fork_copy: linked dll data/bss pass 0 failed,
0xF1E000..0xF3E794, done 0, windows pid 16636, Win32 error 998
5046825 [main] perl 18760 fork_copy: linked dll data/bss pass 0 failed,
0xF1E000..0xF3E794, done 0, windows pid 180, Win32 error 998
10094010 [main] perl 18760 fork_copy: linked dll data/bss pass 0 failed,
0xF1E000..0xF3E794, done 0, windows pid 15560, Win32 error 998
15133523 [main] perl 18760 fork_copy: linked dll data/bss pass 0 failed,
0xF1E000..0xF3E794, done 24576, windows pid 18032, Win32 error 299
20176456 [main] perl 18760 fork_copy: linked dll data/bss pass 0 failed,
0xF1E000..0xF3E794, done 0, windows pid 13908, Win32 error 998
25223284 [main] perl 18760 fork_copy: linked dll data/bss pass 0 failed,
0xF1E000..0xF3E794, done 0, windows pid 19892, Win32 error 998
30279016 [main] perl 18760 fork_copy: linked dll data/bss pass 0 failed,
0xF1E000..0xF3E794, done 24576, windows pid 10168, Win32 error 299
0 [main] perl 19868 open_stackdumpfile: Dumping stack trace to
perl.exe.stackdump
aclocal-1.12: error: autom4te terminated by signal: 11
Makefile:455: recipe for target `../src/aclocal.m4' failed
make: *** [../src/aclocal.m4] Error 1
Hi Dan,
those errors look nasty. Maybe some issue with memory management. First
thing to try is a reboot. If that doesn't sort it out then you need to look
at the Windows Event Log for recent items in the "Critical" or "Error"
category.
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
