On 06/03/2017 14:51, Dan Malcolm wrote: > What to do? Since I have the MinGW Installation Manager I guess I could > install everything it offers, but it may be installed in the wrong place to > do any good. Thinking of our email exchanges it seems you expect a lot of > utilities to be available and available in a particular place. Is it > possible that something went missing during my initial package installation?
Hi Dan, I need to clarify a few things. Firstly MinGW is Windows port of the GNU compilers. These are essential as we use them to build WSJT-X. You get a version of them as part of the Qt install and they match the compilers used to make the Qt libraries and tools. This in turn is essential so that projects like WSJT-X can use them and be compatible with the Qt libraries. We also use the Hamlib project for rig control. Unlike Qt which just needs MinGW compilers, Hamlib uses the fairly standard autotools as well that thousands of Open Source projects use. For autotools to work a Unix like shell environment is required and there is one available that goes with MinGW, it is called msys. Msys provides a command shell and many utilities that would be found on a Unix like system. The problem with DLL load addresses is a Microsoft issue in that they use a binary format that is not position independent. I have no idea why DLLs suddenly stop working with fork() emulations, it just happens sometimes. The cure is to rebase the relevant DLLs, rebasing in this context is looking at the size of each DLL and allocating a unique load address hint to each one so that none ever need to be loaded at a different address due to overlapping, at least until whatever causes this happens again. It is this loading into a process virtual address space at a different address that causes the fork() emulations to fail. It appears that the JTSDK does not provide enough of the msys environment to run this rarely required utility, that I tried to help you with but I am largely working blind as I do not use the JTSDK and do not wish to install it due constraints of other projects. Believe me that rebaseall is what you need, it is designed to resolve exactly this issue with one simple command invocation. It is quite possible to install each of the required tools and libraries that are needed to build WSJT-X individually. Greg has taken the time to build a relatively simple to use package that obviates the user from understanding and doing all this work. He provides the minimum needed to do the most basic build tasks which works well for almost everyone. In your case you have hit an issue that needs a deeper understanding and more components to resolve. I am afraid that using standard tools for software development is complex and usually messy, you are living in a charmed world where someone like Greg has smoothed down all the sharp edges for you but nearby there be dragons and one of them has walked out of the forest in your direction. 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
