On 2015-04-19 14:15-0000 Arjen Markus wrote: > Hi Alan, > > > >> -----Original Message----- >> From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca] >> >> When rewriting this PATH manipulation logic after the 5.11.0 release I >> screwed up >> one aspect (forgot the nondynamic case), and your test found that script >> bug. Sorry >> about that! Please try again (for commit id c689ff3 which fixes this issue). >> >> Regardless of success or failure, full report please. >>
> Yes, that change did the trick - the (restricted) completed without a > problem. See the attached tarball. That is good news indeed. So it appears we finally have a good baseline result for Cygwin without any brute force changes. I am well aware you have been contributing a lot of your time to achieve these improved and extremely valuable comprehensive testing results not only for Cygwin but also MinGW/MSYS so thanks very much for this effort! So since you have been working so hard at this, I want to emphasize any further requests are very much for "whenever your time constraints permit". But if you do have more time to continue now please run this test again with less narrow restrictions. That is, remove the current --do_ctest no --do_test_traditional_install_tree no --do_test_interactive no options until you run into an issue. I think ctest worked fine for you before so that should not be an issue. Furthermore, my latest traditional build fix for Ubuntu, might also have solved the do_test_traditional_install_tree issues you were running into before. And if that works, then that just leaves the interactive issue you discovered which was (I believe) X was not connecting properly. Anyhow, I hope you can figure that out since I believe you did get the xwin device to work (but quite slowly) in previous Cygwin tests. But if you cannot figure out the X problem, perhaps we should add a build-system option to disable X so you can use that and also allow interactive tests of, e.g., the wingcc and ntk devices which are not X based? Once removing the above restrictions works (or can be narrowed down to disabling X11 on Cygwin) (and again if your current time constraints permit) you should also look carefully at the WARNING messages in shared/output_tree/cmake.out to see why so many components of PLplot are being dropped. The most important of these WARNING messages are as follows: -- WARNING: swig not found. Disabling java bindings -- WARNING: swig not found. Disabling Python bindings -- WARNING: swig not found. Disabling Octave bindings -- WARNING: Disabling Itcl interface code -- WARNING: setting ENABLE_tk to OFF -- WARNING: no working Ada compiler so disabling Ada bindings and examples. -- WARNING: swig not found. Disabling Lua bindings -- WARNING: no working D compiler so disabling D bindings and examples. -- WARNING: qhull library not found. Setting PL_HAVE_QHULL to OFF. -- WARNING: pango, pangoft2, or lasi not found with pkg-config. -- WARNING: wxWidgets or its libraries not found so setting all wxwidgets devices to OFF. -- WARNING: Setting PLD_pdf to OFF. -- WARNING:ocamlc not found. Disabling ocaml bindings You will have to check the context of these warning messages for why certain Tcl/Tk/Itcl/Itk components were disabled. For example, Tk was dropped because of a Tk version inconsistency discovered by the PLplot build system so to enable Tk again you will have to figure out why that inconsistency is occurring. With regard to the non Tcl/Tk/Itcl/Itk warnings, I have just checked the python x86_64 packages at <http://cygwin.com/cgi-bin2/package-grep.cgi> which allows a very nice regular expression search of package names and files within the packages. I urge you to try such searches for yourself. My search for "gdc" (the D compiler) and "haru" and "hpdf" (possible names for the library prerequisite for the pdf device driver) did not turn up anything relevant. So -- WARNING: no working D compiler so disabling D bindings and examples. -- WARNING: Setting PLD_pdf to OFF. are likely a lost cause on Cygwin. However, my searches for the terms swig, (and java, python, octave, and lua, if they are not installed already on your Cygwin platform), qhull, ada, lasi, wx, and ocamlc all found something relevant so with some care in selecting the packages to install most of the above warnings should go away and, for example, the following list of current disabled bindings ENABLE_ada: OFF ENABLE_java: OFF ENABLE_lua: OFF ENABLE_ocaml: OFF ENABLE_octave: OFF ENABLE_python: OFF ENABLE_pyqt4: OFF ENABLE_itcl: OFF ENABLE_tk: OFF ENABLE_itk: OFF ENABLE_wxwidgets: OFF should all be ON and part of the (much broader) comprehensive test unless you must explicitly disable these components because they don't work for some reason, and, of course, finding out which components currently don't work is the whole point of these tests. Once all relevant Cygwin packages are installed and the script (with PLplot components which you have dropped) completes with no issues, then (again as time permits) we can start jointly working on the build system bugs for Cygwin your dropped components reveal so that these dropped components can be reinstated again one by one without messing up the comprehensive test. In sum, you have made an excellent start with Cygwin, but as time permits I hope you deal with these remaining issues with the final goal of having a comprehensive test success with all possible components of PLplot enabled which would make PLplot on Cygwin essentially just as powerful as it is on Linux. 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
