On 2015-02-11 12:09-0000 Arjen Markus wrote: > Hi Alan, > > > > As promised, I have just committed my work. There are two things left to do: > > - Get rid of the spurious PostScript commands in the Fortran example
Hi Arjen: Actually those were not extra PostScript commands. Instead, if you visually compared those Tcl and Fortran results with the corresponding C result you would have seen the only issue was you forgot to set the rosen variable in both the Tcl and Fortran cases to false to follow what is now done for the C case. I made that tiny fix (commit e674d4f7) and all is well now. ==> adathick, ada, and ocaml are our only language platforms that still have propagation issues. > - Test it on the MinGW platform. The only reason I have not yet done so is that my installation of MinGW is busted (very curious behaviour of the make utility). I will have to reinstall it. Sigh Yes please on comprehensive testing on both the MinGW and Cygwin platforms. Assuming all is well on those platforms, then scripts/comprehensive_test.sh should take roughly two hours to run on either platform for Microsoft Windows. (It only takes an hour on Linux, but I make this two-hour estimate based on the assumption that Microsoft Windows should be roughly the same speed as Linux, and your test laptop is roughly a factor of two slower than my PC.) As you know, I have successfully run that script on MinGW/Wine in the past but it was incredibly slow compared to Linux. Thus, if you took over comprehensive testing on MinGW with your relatively fast Microsoft Windows platform it (a) should not take a huge amount of cpu time for that platform, and it (b) would save me a huge amount (days!) of cpu time on the extremely slow Wine platform. Of course, in the past you have had trouble setting Unix environment variables on Cygwin so your attempt to run scripts/comprehensive_test.sh there failed. But instead of using some Windows GUI to set Windows environment variables (which may not propagate correctly to Cygwin Unix) I suggest you simply use the Unix command-line syntax (available on bash and other Unix shells) export PATH=<whatever> to set your PATH environment variable appropriately, and similarly for other required environment variables such as CMAKE_INCLUDE_PATH, etc. Also, once you settle on the Unix environment variables you want to set, you can put all the necessary export commands into a file and run the command source <filename> to do the equivalent of typing all commands (such as the export commands) that are in that file. See cmake/epa_build/setup/setup_linux_makefiles for an example of a file to be source'd this way. (Of course, that example is relevant to epa_build so it does more than you need with PLplot if you are simply running scripts/comprehensive_test.sh on the command line.) 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
