From: Arjen M. <Arj...@de...> - 2017-08-15 07:11:16
|
Hi Alan, > -----Original Message----- > From: Alan W. Irwin [mailto:ir...@be...] > Sent: Friday, August 11, 2017 6:33 PM > > Once you perform (1), (2'), and (3), I should have two report tarballs to look at as > well as one ~62MB tarball collection of plot file results, and assuming those reveal > no more issues (other than the "missing pyqtconfig.py" issue we will be dealing with > after the release), then these should be the last noninteractive tests you need to > make on this platform before the release. > This is turning out to be very frustrating - a sort of spring procession of Echternach. While my installation of MinGW-w64/MSYS2 is clean (I did not mess with it other than via pacman), I thought it would be a good idea to do a parallel installation anyway - as a test for my automated installation procedure and as future help to others. So: - The automated installation went fairly smooth, but CMake did not acknowledge the MSYS or Unix generators that my original installation did have. - I had to resort to the MinGW generator, but then you have to move "sh.exe" out of the way. - I had some trouble getting "git" to be available via the MinGW-w64/MSYS2 shell - I later realised that was my fault. So I corrected that this morning by expanding the PATH correcrly. Only to discover that the git installation then brings in its own "sh.exe". - Yesterday I got stuck because CMake was invoking the MicroSoft version of make - despite the fact that "which make" in the MinGW-w64/MSYS2 shell reports "/usr/bin/make". The MicroSoft make utility does not do anything useful with the makefiles as they are generated by CMake in this constellation :(. Except perhaps causing the process to hang. - I realised, however, that I could instruct the comprehensive test script to explicitly use "/usr/bin/make". So I added that option to the invocation. - To my surprise CMake did acknowledge the "MSYS generator" this morning (*), but because I had moved "sh.exe" out of the way, "/usr/bin/make" refused to do its job, as it could not find the "sh.exe" executable. So CMake failed. Sigh. Sorry to sound so grumpy, but it was rather frustrating as I already said. The whole thing is requiring more of my attention than I can actually spare for the next few days (I have to revise an article and that is mostly in my spare time). I will try to get bits and pieces of the tests done inbetween all other stuff, but I am not going to promise anything as far as time of delivery is concerned. Regards, Arjen (*) MinGW-w64 seems to require that you restart the shell after installing things if you want to take full advantage of the freshly installed package. That may be an explanation for yesterday's failure with CMake. A small mistake in my install script required me to install CMake manually. DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail. |