Hi Greg: It's important our interchanges remain on list so others can benefit from them so please don't drop the list Cc from your replies.
Thanks for all these test results. More below in context On 2015-03-28 16:27-0700 Greg Jung wrote: > HI Alan, > > I did use make all on that run, but probably the issue was that the > testing instructions were > not simple and specific enough. > > ok so from an empty subdirectory of the source directory I ran the script > from MSYS2: For my records and for others here that might be interested in MSYS2, could you describe the origin/version of this MSYS2? Is this MinGW-w64/MSYS2 that you can install following the procedure given in <https://sourceforge.net/p/msys2/wiki/MSYS2%20installation/>? Even if you confirm that, there are several possible different options you can take so a full description of your MSYS2 install would be best. > Each of the steps in this comprehensive test may take a while.... > cmake in the build tree > make -j4 VERBOSE=1 in the build tree > ctest -j4 in the build tree > ERROR: ctest -j4 failed in the build tree On the assumption that the above results were for the very first (shared library) part of the comprehensive test, could you pack up everything in comprehensive_test_disposeable/shared/output_tree/ into a compressed tarball and send it here as an attachment to help me figure out what is going wrong with ctest? > [...]So I try now with Mingw.org msys: > Each of the steps in this comprehensive test may take a while.... > cmake in the build tree > make -j4 VERBOSE=1 in the build tree > > This seems hung, even though the activity indicators seem to be > going. Parallel builds hang on MinGW/MSYS due to a very long-standing bug for that platform. To work around that MinGW/MSYS bug you have to use the --build_command make option (i.e., drop the -j4 option for make) for the scripts/comprehensive_test.sh command. That, of course, is going to slow the comprehensive test for MinGW/MSYS, but your report for that platform would be most welcome, and I hope you will achieve complete success there (like I did much earlier in this release cycle although I hope to confirm that again for myself for the master tip version in the next several days). > from linux: > I got a clean bill of health under OpenSuse13.2 wx 3.0/ gtk2u > > Each of the steps in this comprehensive test may take a while.... > cmake in the build tree > make -j4 VERBOSE=1 in the build tree > ctest -j4 in the build tree > make -j4 clean_ctest_plot_files in the build tree (since we are done with > ctest) > make -j4 VERBOSE=1 test_noninteractive in the build tree > make -j4 VERBOSE=1 install in the build tree > make -j4 clean in the build tree (since we are done with it at least > for the non-interactive test case) > Prepend > /home/plplot-5.11/../comprehensive_test_disposeable/shared/install_tree/bin > to the original PATH > cmake in the installed examples build tree > make -j4 VERBOSE=1 test_noninteractive in the installed examples build tree > make -j4 clean in the installed examples build tree (since we are done > with it at least for the non-interactive test case) > Traditional make -j4 test_noninteractive in the installed examples tree > Traditional make -j4 clean in the installed examples tree (since we > are done with it at least for the non-interactive test case) > make -j4 VERBOSE=1 test_interactive in the build tree > ERROR: make -j4 test_interactive failed in the build tree (I'm > deleting open windows at this stage, shutting down) Hmm. Letting the whole OpenSuse13.2 comprehensive test complete would be extremely worthwhile also since I don't think we have ever seen a complete comprehensive test for that variant of Linux. > I'll go back to windows and see whats up there, now that I know what I > should be seeing. > > OK CygWIN(64) is a bust - make has a problem. tarball of comprehensive_test_disposeable/shared/output_tree? > /mingw64/ via Msys2 - make sailed through, same ctest failure. > /mingw32/ via msys2 - make is ok, ctest has hung with no discernable > activity, on c++/x00: I thought you reported MSYS2 results above. Are you referring to a different platform there as opposed to the two platforms here? Anyhow, more descriptive details concerning these various platforms you are reporting are essential. In any case, whenever there is a problem, please collect everything in comprehensive_test_disposeable/shared/output_tree, comprehensive_test_disposeable/nondynamic/output_tree, and comprehensive_test_disposeable/static/output_tree in a tarball (the latter two directories only if you get that far). Also, please exclude everything else from the tarball because it would be too large. Thanks again for attempting all this testing for a large number of different platforms, and I look forward to your several different output_tree tarball replies, and also a report from you that when you let the OpenSuse version actually finish, that you obtained comprehensive testing success with that platform (and similarly for MinGW/MSYS if you drop the -j4 option to make as I describe above). 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. 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
