On 2015-04-05 11:55-0700 Alan W. Irwin wrote: > On 2015-04-05 11:14-0000 Arjen Markus wrote: > >> Hi Alan, >> >> >> >> Attached is the stderr/stdout output from the script. >> >> >> >> The script itself was: >> >> >> >> export >> PATH=/cygdrive/d/plplot-svn/comprehensive_test_disposeable/shared/install_tree/bin:$PATH >> >> export >> PATH=/cygdrive/d/plplot-svn/comprehensive_test_disposeable/shared/install_tree/lib/plplot5.10.0/drivers:$PATH >> >> ../plplot-git/scripts/comprehensive_test.sh >> --do_test_traditional_install_tree no --do_test_interactive no >> >> >> >> I am not sure if both extensions of the PATH variable are required, but at >> least with the two it worked. At the very least the second was required. > > Although the above brute-force changes to the PATH, may work, there > are not ideal since they impose install-tree results on build-tree > tests.
> [...]I think the solution is to drop this problematic logic completely and > instead introduce one more option to the script called > --manipulate_PATH which defaults to no but which Windows platform > users should specify as yes. But I will deal with that issue > post-release, and for now the Cygwin results you have obtained with > the above brute-force approach are good enough. Hi Arjen: I think I have found a good bash shell method of automatically detecting any windows platform (using the "exe" suffix that occurs for the bash fullpathname on all Windows platforms). So there is no need for the user to specify whether Windows PATH manipulation is needed or not and therefore no need to implement the above --manipulate_PATH option for the script. As of commit id 13a3baa, I have changed the script to implement the automatic Windows platform detection described above. That means path manipulations will automatically occur on all Windows platforms within the script and there is no longer any need to use brute-force PATH changes before running the script on Cygwin (or any other Windows platform). Could you let me know if the fix works (i.e., by running the script with no special brute-force PATH manipulations beforehand). This might also be a good opportunity for you to permanently remove some of the constraints on your prior successful Cygwin test. For example, note (E) on your current test report at <https://sourceforge.net/p/plplot/wiki/Testing_PLplot/#Testing%20Reports> implies if you install swig on your Cygwin platform, the Java, Python, Octave, and Lua components of PLplot will be included in your comprehensive testing (assuming you have the development versions of those software packages already installed). 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
