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. So to investigate further about why that brute-force method was required I looked at your script output which has now given me enough information to confuse me. :-) If you look at scripts/comprehensive_test.sh for anything to do with PATH you should notice logic there that puts the build-tree dll subdirectory on the PATH when doing build tree tests, but that part of the PATH is dropped (rightly) for install tree tests where instead components are added to the PATH so the installed (not build-tree) dlls will be found and the installed drivers will be found. That logic works great for me in the MinGW or MinGW/MSYS case. However, I have now noticed that the if statements that introduce those PATH manipulations tests whether the generator string is either "MSYS Makefiles" or "MinGW Makefiles" so the currently logic should not work at all for Cygwin where the generator string must be "Unix Makefiles". That is clearly a bug in the script that should be fixed so you don't have to use the brute-force approach above. The confusing part for me is I would have predicted that none of those PATH manipulations would work on Cygwin, yet your script output clearly says Prepend /cygdrive/d/plplot-svn/plplot-git/../comprehensive_test_disposeable/nondynamic/install_tree/bin to the original PATH which means the script executed logic in what I think would be an impossible if block to access under Cygwin. Later on, it did not exercise the if block with further PATH logic which is the reason you had to use the above brute-force method. Anyhow, the point is the current logic for deciding whether to do PATH manipulations is problematic. 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. 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
