Mingw/msys: Because I have cmake modified to look in /usr/local and such for libraries and such (not a good idea, I know now), I added the option --cmake_command to the script and used
--cmake_command=/d/path-to-cmake/bin/cmake.exe and the make completed ok but the ctest hung at example/c/x00c; I had to kill the process. I'm sending gzipped- tar files to you separately because the list filters may kill the message altogether. About Msys/Msys2: I suppose there are 4 distinct platforms I use in Windows: Msys2 with minw32/, with mingw64/, and msys1 with mingw standard (mingw.org). And cygwin64. For the purposes of these tests I'll label them mingw32, mingw64, and mingworg. Msys or cygwin run posix compatibility layers and maintain their own "mounted" file systems within windows' file system. They can also interpret windows-style pathnames. Both Msys are derived from cygwin. Cygwin tries hard to be "your unix in the dos-box" but msys is avowedly limited in scope to the support of cross-compilations of UNIX builds on the windows' platform. To do this it generally snoops on the command line and looks for likely places that filenames would benefit from translation from the msys-mounted to the win-style, i.e. /usr/lib becomes D:/path-to-msys/lib. For cygwin, everything is kept in posix-style notation. As far as msys goes, msys2 is built to be 64-bit, to keep up better with the modern cygwin layer. Msys2 uses a pacman-based packaging update system, https://sourceforge.net/p/msys2/wiki/MSYS2%20installation/ The default configuration is, /msys64 toplevel directory which becomes "/". GCC toolchain, complete with support libraries, are installed from the mingw-w64 project into /mingw64 and, for native 32-bit builds, /mingw32. The big convenience for me, besides the pre-built libraries, was that someone decided which exception and thread models to use!! (I suppose they could be swapped out if needed). On Sun, Mar 29, 2015 at 10:01 AM, Alan W. Irwin <ir...@beluga.phys.uvic.ca> wrote: > On 2015-03-28 22:20-0700 Alan W. Irwin wrote: > >> Also, when you report back again, will you please always specify the >> scripts/comprehensive_test.sh options you used in every different >> platform case? The easiest way to do that is to always include >> everything output from the script rather than bits and pieces like >> above. So ideally you would capture the whole output from the script >> in a file, compress that file, and attach it to your post here (as >> well as tarballs of comprehensive_test_disposeable/shared/output_tree, >> comprehensive_test_disposeable/nondynamic/output_tree, and >> comprehensive_test_disposeable/static/output_tree) for each platform >> you test. > > > Hi Greg: > > One other point I should have mentioned is you should use a different > --prefix option for each separate run of scripts/comprehensive_test.sh > to keep your comprehensive testing results for various platforms (if > done on the same computer) completely separate from each other. > > > Alan > __________________________ > Alan W. Irwin > > Astronomical research affiliation with Department of Physics and Astronomy, > University of Victoria (astrowww.phys.uvic.ca). > > Programming affiliations with the FreeEOS equation-of-state > implementation for stellar interiors (freeeos.sf.net); the Time > Ephemerides project (timeephem.sf.net); PLplot scientific plotting > software package (plplot.sf.net); the libLASi project > (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); > and the Linux Brochure Project (lbproject.sf.net). > __________________________ > > Linux-powered Science > __________________________ ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
