On 2015-04-19 15:08-0000 Arjen Markus wrote: > [.... B]y running the example as built in the comprehensive_test_disposeable directory, I found what was wrong: my script did not set the PLPLOT_DRV_DIR environment variable, so that the example could not detect which drivers were available. After correcting that (I must have set it in the shell before, rather than via the script), the example worked and now the script is happily running.
Hi Arjen: That is a pretty cool automated script for running the test and collecting all relevant results into a tarball. The only thing I would add to it is rm -rf ../comprehensive_test_disposeable right at the start so there are no stale results left in that directory from previous runs of the script. By looking at env.out, and also your script I find you have set 1. PLPLOT_DRV_DIR=/d/plplot-svn/comprehensive_test_disposeable/shared/build_tree/drivers 2. PLPLOT_LIB=/d/plplot-svn/plplot-git/data 3. PL_LIBRARY=/d/plplot-svn/plplot-git/bindings/tk None of those should be necessary, and mean that when you are purportedly testing the installed examples tree, you are actually (1) using drivers from the (shared only) build tree, (2) data from the source tree, and (3) Tk results from the source tree(?). That is, all of these are brute-force workarounds for MinGW/MSYS that I don't need to use here and which we should figure out how to avoid in your case. So you have actually changed 3 things between the test that succeeds and the one that does not. Let's deal with 2 and 3 later, but if you leave 2 and 3 in place, do you really need 1? The reason I ask is your script output clearly documents Prepend /d/plplot-svn/plplot-git/../comprehensive_test_disposeable/shared/build_tree/dll to the original PATH occurs before anything happens in the build tree for the shared case and Prepend /d/plplot-svn/plplot-git/../comprehensive_test_disposeable/shared/install_tree/bin to the original PATH Prepend /d/plplot-svn/comprehensive_test_disposeable/shared/install_tree/lib/plplot5.11.0/drivers to the current PATH occurs before anything happens in the installed examples build tree for the shared case. So as long as those directories are properly populated with the dll part of shared libraries and the device driver dll's, then all should be well and you should not need 1 at all. To help figure this out if 1 is absolutely needed in your case, then I need you to run the script again as before (with 1, 2, and 3 set and with your present script options set) with the following additional script options: --do_clean_as_you_go no This option means the script does not clean up the interesting results. Therefore, with this option the file lists that you include in your tarball reflects what is there in /d/plplot-svn/comprehensive_test_disposeable/shared/build_tree/drivers and also /d/plplot-svn/comprehensive_test_disposeable/shared/build_tree/dll (the directory put on the PATH by the script) when the test is being executed without any subsequent cleanup to remove the interesting stuff. However, the above option does have the potential to consume a lot of disk space (something roughly like 50GB for a complete comprehensive test on fully loaded Linux systems, but presumably a lot less than that on MinGW/MSYS system missing many PLplot soft dependencies). Thus, if you are short of spare disk space, you _could_ temporarily narrow the tests as much as possible by, e.g., dropping all but the shared case --do_nondynamic no --do_static no Also, you could narrow the tests even further by limiting all results to just C tests for just the ps devices by specifying --cmake_added_options "-DDEFAULT_NO_BINDINGS=ON -DDEFAULT_DEFAULT_NO_DEVICES=ON -DPLD_psc=ON -DPLD_ps=ON" But whether or not you set these last three options is up to you depending on any concerns you might have concerning disk space. In sum, I think we are making good progress on MinGW/MSYS with only 3 brute force workarounds left to deal with on your MinGW/MSYS platform that are not required on mine. But some more experiments with running the script (with a complete automated tarball report for each case) should soon sort out what the issues are on your MinGW/MSYS platform. 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 __________________________ ------------------------------------------------------------------------------ BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
