On Jan 12, 2016, at 12:00 PM, Ross Berteig <[email protected]> wrote: > > On 1/12/2016 8:41 AM, LM wrote: > >> .... >> >> I'm not sure if my build of Fossil is using relevant system libraries. >> > > On Windows, the best way to check for errant DLL references is with DEPENDS.
That’s not a standard part of Windows. It is included in several different development packages from Microsoft, but someone using MinGW may be trying to avoid installing those. There’s a third-party site that offers it for download if you’d rather not chase down the DDK or another source for it, but I cannot recommend it, since I don’t know who these guys are, what their motivations are, or how well they’ve protected themselves against distributing trojanned versions: http://www.dependencywalker.com/ A more trustworthy source would be Microsoft itself, but that probably means downloading dozens of megs of unrelated stuff. (DDK, SDK, etc.) Some of the SysInternals tools can do similar things, like listdlls: https://technet.microsoft.com/en-us/sysinternals/bb896656 Or, use ldd from Cygwin, as I do. > I just checked my built fossil.exe, and DEPENDS lists only the expected > system libraries (ADVAPI32.DLL, KERNEL32.DLL, MSVCRT.DLL, WS2_32.DLL) and no > unexpected DLLs. $ ldd fossil.exe ntdll.dll => /cygdrive/c/WINDOWS/SYSTEM32/ntdll.dll (0x7ffc5a8a0000) KERNEL32.DLL => /cygdrive/c/WINDOWS/system32/KERNEL32.DLL (0x7ffc58300000) KERNELBASE.dll => /cygdrive/c/WINDOWS/system32/KERNELBASE.dll (0x7ffc57d90000) _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
