Re: [Plplot-devel] Release status: call for comprehensive testing

2015-04-14 Thread Alan W. Irwin
On 2015-04-10 21:54+0100 Andrew Ross wrote: Hazen, That's interesting, and at odds with my tests a week or so back on Kubuntu 14.10. Can you confirm which flavour and version of Ubuntu you are using? Also, I assume this is with Qt4 and not Qt5? Hi Andrew: The answers to your questions

Re: [Plplot-devel] Release status: call for comprehensive testing

2015-04-11 Thread Hazen Babcock
On 04/10/2015 09:06 PM, Alan W. Irwin wrote: On 2015-04-10 12:29-0400 Hazen Babcock wrote: That's a fairly sparse but still acceptable comprehensive test result for this release, but to start the next release cycle properly I strongly encourage everybody here to learn to run the

Re: [Plplot-devel] Release status: call for comprehensive testing

2015-04-10 Thread Andrew Ross
Hazen, That's interesting, and at odds with my tests a week or so back on Kubuntu 14.10. Can you confirm which flavour and version of Ubuntu you are using? Also, I assume this is with Qt4 and not Qt5? Andrew On Fri, Apr 10, 2015 at 12:29:15PM -0400, Hazen Babcock wrote: That's a fairly

Re: [Plplot-devel] Release status: call for comprehensive testing

2015-04-10 Thread Hazen Babcock
On 04/10/2015 04:54 PM, Andrew Ross wrote: Hazen, That's interesting, and at odds with my tests a week or so back on Kubuntu 14.10. Can you confirm which flavour and version of Ubuntu you are using? Also, I assume this is with Qt4 and not Qt5? Andrew, This is what I have: hb ~$ uname -a

Re: [Plplot-devel] Release status: call for comprehensive testing

2015-04-10 Thread Alan W. Irwin
On 2015-04-10 12:29-0400 Hazen Babcock wrote: That's a fairly sparse but still acceptable comprehensive test result for this release, but to start the next release cycle properly I strongly encourage everybody here to learn to run the scripts/comprehensive_test.sh bash script to completion

Re: [Plplot-devel] Release status: call for comprehensive testing

2015-04-10 Thread Alan W. Irwin
On 2015-04-10 21:54+0100 Andrew Ross wrote: [Hazen's poor qt result is] at odds with my tests a week or so back on Kubuntu 14.10. Hi Andrew: Could you please report the details of those good comprehensive test results at https://sourceforge.net/p/plplot/wiki/Testing_PLplot/#Testing%20Reports

Re: [Plplot-devel] Release status: call for comprehensive testing: Cygwin

2015-04-05 Thread Alan W. Irwin
On 2015-04-05 01:17-0700 Alan W. Irwin wrote: On 2015-04-04 23:11-0700 Greg Jung wrote: afaict these environment variables are essential for plots: PLPLOT_DRV_DIR=/usr/local/lib/plplot5.10.0/drivers PLPLOT_HOME=/usr/local/share/plplot5.10.0/ DRV_DIR for dynamic loading, to get the

Re: [Plplot-devel] Release status: call for comprehensive testing: Cygwin

2015-04-04 Thread Arjen Markus
Hi Alan, Greg, -Original Message- From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca] @Greg: You have much more experience with Cygwin than I do (since my actual experience is zero). Nevertheless, historically there has been lots of warnings on the CMake list that Cygwin

Re: [Plplot-devel] Release status: call for comprehensive testing: Cygwin

2015-04-04 Thread Arjen Markus
Hi Alan, -Original Message- From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca] Sent: Saturday, April 04, 2015 9:04 PM To: Arjen Markus Cc: Greg Jung; Phil Rosenberg; Jim Dishaw; PLplot development list Subject: RE: Release status: call for comprehensive testing: Cygwin Hi

Re: [Plplot-devel] Release status: call for comprehensive testing

2015-04-03 Thread Arjen Markus
03, 2015 7:57 AM To: Alan W. Irwin Cc: PLplot development list Subject: Re: [Plplot-devel] Release status: call for comprehensive testing This is a long-standing cygwin warning, CMake no longer defines WIN32 on Cygwin! for those rip-van-winkles coming back to cygwin and somehow wanting WIN32

Re: [Plplot-devel] Release status: call for comprehensive testing: Cygwin

2015-04-03 Thread Greg Jung
In Cygwin, I do use the cygwin cmake; but it isn't distributed by cygwin, I built it from source. At one point I tried the windows cmake from cygwin and it failed miserably. On Fri, Apr 3, 2015 at 12:20 PM, Alan W. Irwin ir...@beluga.phys.uvic.ca wrote: On 2015-04-02 22:57-0700 Greg Jung wrote:

[Plplot-devel] Release status: call for comprehensive testing: Cygwin

2015-04-03 Thread Alan W. Irwin
On 2015-04-02 22:57-0700 Greg Jung wrote: This is a long-standing cygwin warning, CMake no longer defines WIN32 on Cygwin! for those rip-van-winkles coming back to cygwin and somehow wanting WIN32 to be defined. I am very familar with the possible quirks that can arise with Cmake; if there

Re: [Plplot-devel] Release status: call for comprehensive testing: MinGW-w64/MSYS2

2015-04-03 Thread Greg Jung
The cmake I specify for MSYS is a vanilla cmake downloaded from cmake.org; I use this because all of my other CMakes use scripts I modified. Cmake for Msys needs to use msys make, not mingw32-make; otherwise you want to do a mingw build which involves hiding sh from the PATH, using CMD.exe, etc.

Re: [Plplot-devel] Release status: call for comprehensive testing: Cygwin

2015-04-03 Thread Alan W. Irwin
On 2015-04-03 14:06-0700 Greg Jung wrote: In Cygwin, I do use the cygwin cmake; but it isn't distributed by cygwin, I built it from source. At one point I tried the windows cmake from cygwin and it failed miserably. @Greg: Thanks for that clarification. I agree that cmake built on Cygwin

[Plplot-devel] Release status: call for comprehensive testing: wxwidgets

2015-04-03 Thread Alan W. Irwin
I have just finished (once again) a complete test of wxwidgets for all our standard examples. I have reported the results (which are quite encouraging) at the (re-edited) https://sourceforge.net/p/plplot/bugs/151/. It's this bug report I will refer to in the release notes. Freeze and release

Re: [Plplot-devel] Release status: call for comprehensive testing

2015-04-02 Thread Greg Jung
This is a long-standing cygwin warning, CMake no longer defines WIN32 on Cygwin! for those rip-van-winkles coming back to cygwin and somehow wanting WIN32 to be defined. I am very familar with the possible quirks that can arise with Cmake; if there is a systemic failure it generally blows up in

Re: [Plplot-devel] Release status: call for comprehensive testing

2015-04-02 Thread Alan W. Irwin
On 2015-03-30 12:42-0700 Alan W. Irwin wrote: There is a big warning in plplot-cygwin/output_tree/cmake.out (for version 3.0.1) about CMake no longer defines WIN32 on Cygwin! Hi Greg: I believe I have now found the source of that warning message which is (according to cmake mailing list

Re: [Plplot-devel] Release status: call for comprehensive testing

2015-03-31 Thread Arjen Markus
Hi Alan, -Original Message- From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca] @Arjen and Phil, will both of you please look at the cygwin.tgz attachment? There is a big warning in plplot-cygwin/output_tree/cmake.out (for version 3.0.1) about CMake no longer defines WIN32

Re: [Plplot-devel] Release status: call for comprehensive testing

2015-03-31 Thread Arjen Markus
Hi Alan, @Arjen and Phil, will both of you please look at the cygwin.tgz attachment? There is a big warning in plplot-cygwin/output_tree/cmake.out (for version 3.0.1) about CMake no longer defines WIN32 on Cygwin! Have either of you run into this issue for CMake on Cygwin? There is

Re: [Plplot-devel] Release status: call for comprehensive testing

2015-03-31 Thread Alan W. Irwin
On 2015-03-31 09:33- Arjen Markus wrote: Hi Alan, @Arjen and Phil, will both of you please look at the cygwin.tgz attachment? There is a big warning in plplot-cygwin/output_tree/cmake.out (for version 3.0.1) about CMake no longer defines WIN32 on Cygwin! Have either of you run into

Re: [Plplot-devel] Release status: call for comprehensive testing

2015-03-31 Thread Alan W. Irwin
On 2015-03-31 11:05-0700 Greg Jung wrote: Here is tarball og the output directory from recent fully-completed Suse-13.2 test. I did terminate interactive testing at the end, by killing windows, the strip chart was going very slow. But the wx Viewers looked great. Hi Greg: Thanks very much

Re: [Plplot-devel] Release status: call for comprehensive testing

2015-03-31 Thread Alan W. Irwin
On 2015-03-31 09:31-0700 Alan W. Irwin wrote: Hi Arjen: Gack. I am really glad you found this bug in setting the -DUSINGDLL compile flag for libplplotqt source files (and also for smoke bindings) for the static library case. This bug was caused by a commit made by me back in 2013. One of

Re: [Plplot-devel] Release status: call for comprehensive testing

2015-03-31 Thread Greg Jung
Here is tarball og the output directory from recent fully-completed Suse-13.2 test. I did terminate interactive testing at the end, by killing windows, the strip chart was going very slow. But the wx Viewers looked great. On Tue, Mar 31, 2015 at 9:31 AM, Alan W. Irwin

Re: [Plplot-devel] Release status: call for comprehensive testing

2015-03-30 Thread Greg Jung
Mingw/msys: Because I have cmake modified to look in /usr/local and such for libraries and such (not a good idea, I know now), I added the option --cmake_command to the script and used --cmake_command=/d/path-to-cmake/bin/cmake.exe and the make completed ok but the ctest hung at example/c/x00c;

Re: [Plplot-devel] Release status: call for comprehensive testing

2015-03-30 Thread Alan W. Irwin
On 2015-03-30 12:14-0700 Alan W. Irwin wrote: On 2015-03-30 10:40-0700 Greg Jung wrote: Here are gzipped- tar files sent separately because the list filters may kill the message altogether. Our mailing list does not kill tarballs in my experience. So to test that in this case, I am

Re: [Plplot-devel] Release status: call for comprehensive testing

2015-03-29 Thread Alan W. Irwin
On 2015-03-26 18:50-0700 Alan W. Irwin wrote: With commit id 5f6e28f I finally have been able to complete scripts/comprehensive_test.sh on Linux without issues which removes the last known regression compared to 5.10.0 for this release which is a much-desired result. My next steps are [1]

Re: [Plplot-devel] Release status: call for comprehensive testing

2015-03-29 Thread Jim Dishaw
On Mar 29, 2015, at 9:17 AM, Andrew Ross andrewr...@users.sourceforge.net wrote: Also -np to prevent pausing between pages doesn't work. This is not a major issue, but is a slight pain when running the automatic tests. Andrew I believe this bug might be related to the extra

Re: [Plplot-devel] Release status: call for comprehensive testing

2015-03-29 Thread Andrew Ross
On Sat, Mar 28, 2015 at 05:41:12PM -0700, Alan Irwin wrote: On 2015-03-28 21:40- Andrew Ross wrote: I use 2.2.1 as well but with additional patches applied. See cmake/epa_build/libharu/CMakeLists.txt for how to locate those patches. Most of those are to install a CMake-based build

Re: [Plplot-devel] Release status: call for comprehensive testing

2015-03-29 Thread Alan W. Irwin
On 2015-03-28 22:20-0700 Alan W. Irwin wrote: Also, when you report back again, will you please always specify the scripts/comprehensive_test.sh options you used in every different platform case? The easiest way to do that is to always include everything output from the script rather than

Re: [Plplot-devel] Release status: call for comprehensive testing

2015-03-28 Thread Andrew Ross
On Sat, Mar 28, 2015 at 09:07:46PM +, Andrew Ross wrote: Alan, For me with Ubuntu 14.10 (Utopic Unicorn) scripts/comprehensive_test.sh fails. Compile all goes fine, but the test of the C examples with the pdf driver fails at example 24 with ERROR: error_no=1050, detail_no=0 ERROR

Re: [Plplot-devel] Release status: call for comprehensive testing

2015-03-28 Thread Alan W. Irwin
On 2015-03-28 21:40- Andrew Ross wrote: On Sat, Mar 28, 2015 at 09:07:46PM +, Andrew Ross wrote: Alan, For me with Ubuntu 14.10 (Utopic Unicorn) scripts/comprehensive_test.sh fails. Compile all goes fine, but the test of the C examples with the pdf driver fails at example 24 with

[Plplot-devel] Release status: call for comprehensive testing

2015-03-26 Thread Alan W. Irwin
On 2015-03-25 14:30-0700 Alan W. Irwin wrote: 2. Because of issues like the qt_example segfault that I have just fixed, I have as yet been unable to complete a comprehensive test of PLplot on Linux. Until I can get such a clean test the possibility exists there are other such segfault issues