plplot-devel — Technical discussion about PLplot development

Re: [Plplot-devel] Octave 4.0.0

[Alan W. I. <ir...@be...>]

On 2015-07-11 19:27-0700 Alan W. Irwin wrote:
> [...Y]our build
> success motivates me to expand the epa_build implementation to see how
> far I can get with an epa_build of Octave-4.0.0 and patched versions
> of swig-2 and swig-3.  Assuming I can epa_build all of those, then
> that would allow me to do the above run-time check here for patched
> versions of both swig-2 and swig-3, and thus help build the case to
> get your swig patch (or two variants of that if your patch has to be
> modified for swig-2) into the next official releases of both swig-2
> and swig-3.

Hi Orion:

The current status of this effort is I am done with all the relevant
epa_build configuration, but the result segfaults at run time.

Here is what I have done so far.

1. Implemented an epa_build of lapack and blas.  ctest of that build
passed 100 per cent of all the many tests.

2. Upgraded the epa_build of swig-2.0.11 to swig-3.0.6 with your patch applied.
The result works well with PLplot for the non-octave case.  For
example, the swig-generated Python, Lua, and Java bindings all work
well.

3. Implemented an epa_build of octave_lite which is octave-4.0.0 with
all optional components disabled.  This version passes the simple test

octave:1> x=-pi:0.1:pi;
octave:2> plot(x,sin(x))
octave:3> exit

with the plot done with the default gnuplot.  However, valgrind of
that simple test loses control of octave_lite (see below).

4. epa_built plplot_lite against this octave-lite version with no issues.

5. However, when I try the above simple test in a directory which
contains the following file (to enable the PLplot version of plotting)

wine@raven> cat .octaverc
warning("off","Octave:shadowed-function");
addpath("/home/wine/newstart/build_script/build_dir-linux/epa_build/Source/build_plplot_lite/bindings/octave/PLplot","/home/wine/newstart/build_script/build_dir-linux/epa_build/Source/build_plplot_lite/bindings/octave/PLplot/support","/home/wine/newstart/build_script/build_dir-linux/epa_build/Source/build_plplot_lite/bindings/octave/misc","/home/wine/newstart/build_script/build_dir-linux/epa_build/Source/build_plplot_lite/examples/octave","/home/wine/newstart/build_script/build_dir-linux/epa_build/Source/comprehensive_test_disposeable/shared/build_tree/bindings/octave","/home/wine/newstart/build_script/build_dir-linux/epa_build/Source/comprehensive_test_disposeable/shared/build_tree/bindings/octave/PLplot");
global pl_automatic_replot
pl_automatic_replot=1;

where the form of this file has been suggested by bindings/octave/USAGE

the above simple plot test segfaults (where normally with PLplot built
against octave-3.x.y, this simple test generates a plot using the xwin device).

I would like to do further debugging of this segfault with valgrind,
but somehow valgrind is losing control of octave_lite so never
generates any messages after the normal burst of initial messages and
the commands go the same speed as usual (not the slow speed you
normally get with valgrind) regardless of whether I use gnuplot
(without segfault) or the .octaverc trick above to attempt to use
plplot (with segfault).

Tomorrow I will play with the configuration of the epa_build of
octave_lite to see if I can figure out a way to beat this valgrind
issue.

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
__________________________

[Plplot-devel] Comprehensive test results for MingW-w64/MSYS2

[Arjen M. <Arj...@de...>]

Hi Alan,



I send you the current results for the comprehensive test on MingW-w64/MSYS2, as I found some peculiar things. So this is the result I got yesterday, without the extra bits and pieces I intended to install.



The peculiarities are:

-        There is no wingcc device, because the gdi32 header file and library are missing. I just checked: they appear under /usr/include/w32api and /usr/lib/w32api.

-        I wanted to know if there are many external dependencies (given the remark that MinGW-w64 is building on Cygwin), as that might cause problems distributing executable programs. "ldd" only reported the basic Windows DLLs but it did not report libplplot.dll. Very strange. Oh, and the native Windows tool I use for this type of inquiries reports both libplplot.dll AND msys-2.0.dll.

So there actually is a dependency on MSYS stuff.



Anyway, that is the quick report I can send at this moment.



Regards,



Arjen




DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail.

Re: [Plplot-devel] Octave 4.0.0

[Orion P. <or...@co...>]

On 07/11/2015 08:27 PM, Alan W. Irwin wrote:
> On 2015-07-11 17:52-0600 Orion Poplawski wrote:
>> On 07/10/2015 12:04 PM, Orion Poplawski wrote:
>>>
>>> My fix for octave 4.0,0 support in swig is here:
>>> https://github.com/swig/swig/pull/460
> 
>> plplot 5.11.0 is building fine in Rawhide with a patched swig 3.0.6, octave
>> 4.0.0, and the patch to plplot for swig 3.0.6 doc issue.
> 
> Hi Orion:
> 
> Thanks for that encouraging news with regard to good builds of the
> octave binding of PLplot against Octave-4.0.0.  But I have also been
> concerned about the run-time results as well which you can
> straightforwardly check there by simply running
> 
> cmake .... >& cmake.out
> make test_diff_psc >& test_diff_psc.out
> 
> in an initially empty build tree.
> 
> Normally that test shows there are no differences between the
> octave-generated and C-generated results for all our examples for the
> Octave-3.x.y case.  If running that test there shows the same thing
> for the Octave-4.0.0 case that is a very strong test of our octave
> bindings for that case.
> 
> Regardless of whether you try such a run time check, your build
> success motivates me to expand the epa_build implementation to see how
> far I can get with an epa_build of Octave-4.0.0 and patched versions
> of swig-2 and swig-3.  Assuming I can epa_build all of those, then
> that would allow me to do the above run-time check here for patched
> versions of both swig-2 and swig-3, and thus help build the case to
> get your swig patch (or two variants of that if your patch has to be
> modified for swig-2) into the next official releases of both swig-2
> and swig-3.
> 
> Alan

I'm afraid that the plplot octave tests have been failing for quite a while in
Fedora Rawhide, probably due to gcc 5 as reported back in March.


-- 
Orion Poplawski
Technical Manager                     303-415-9701 x222
NWRA, Boulder/CoRA Office             FAX: 303-415-9702
3380 Mitchell Lane                       or...@nw...
Boulder, CO 80301                   http://www.nwra.com

Re: [Plplot-devel] What exact numpy package have you currently got installed on Cygwin for your comprehensive testing?

[Arjen M. <Arj...@de...>]

Hi Alan,



A recognisable situation :). Just to be sure I checked the version of Numpy - 1.9.2-1 according to the setup program and indeed the path includes /usr/lib/lapack. I never noticed that, I must say, but it is good to know that it has been documented.



Regards,



Arjen

> -----Original Message-----
> From: Alan W. Irwin [mailto:ir...@be...]
> Sent: Sunday, July 12, 2015 9:55 PM
> To: Arjen Markus; Greg Jung
> Cc: PLplot development list
> Subject: Re: [Plplot-devel] What exact numpy package have you currently got
> installed on Cygwin for your comprehensive testing?
>
> On 2015-07-10 21:00-0700 Alan W. Irwin wrote:
>
> > Hi Arjen:
> >
> > I have been helping Greg Jung off list with reproducing your best
> > Cygwin comprehensive test results so far, and he is pretty close, but
> > he is having trouble with inconsistencies between various Cygwin numpy
> > packages he installs and the Cygwin development package for
> > python-2.7.10 that you both use for comprehensive testing.
> >
> > So it would be a big help to him if you answered the question in the
> > subject line.
>
> Never mind.  I just now found
> <https://cygwin.com/ml/cygwin/2014-09/msg00327.html> where the same issue
> Greg had with importing numpy was encountered, and the solution was to put
> /usr/lib/lapack on the PATH.  And I also just now discovered this essential bit of
> Cygwin Python/numpy lore is also documented in
> <http://sourceforge.net/p/plplot/wiki/Setup_cygwin>.  I have now clarified that
> wording a bit. Nevertheless, Greg and I both could have saved several days tussling
> with this if we had remembered to read the relevant PLplot documentation.  Oh well,
> humbled again!
> :-)
>
> 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
> __________________________

DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail.

Re: [Plplot-devel] What exact numpy package have you currently got installed on Cygwin for your comprehensive testing?

[Alan W. I. <ir...@be...>]

On 2015-07-10 21:00-0700 Alan W. Irwin wrote:

> Hi Arjen:
>
> I have been helping Greg Jung off list with reproducing your best
> Cygwin comprehensive test results so far, and he is pretty close, but
> he is having trouble with inconsistencies between various Cygwin numpy
> packages he installs and the Cygwin development package for
> python-2.7.10 that you both use for comprehensive testing.
>
> So it would be a big help to him if you answered the question in
> the subject line.

Never mind.  I just now found
<https://cygwin.com/ml/cygwin/2014-09/msg00327.html> where the same
issue Greg had with importing numpy was encountered, and the solution
was to put /usr/lib/lapack on the PATH.  And I also just now
discovered this essential bit of Cygwin Python/numpy lore is also
documented in <http://sourceforge.net/p/plplot/wiki/Setup_cygwin>.  I
have now clarified that wording a bit. Nevertheless, Greg and I both
could have saved several days tussling with this if we had remembered
to read the relevant PLplot documentation.  Oh well, humbled again!
:-)

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
__________________________

Re: [Plplot-devel] Octave 4.0.0

[Alan W. I. <ir...@be...>]

On 2015-07-11 17:52-0600 Orion Poplawski wrote:
>On 07/10/2015 12:04 PM, Orion Poplawski wrote:
>> 
>> My fix for octave 4.0,0 support in swig is here:
>> https://github.com/swig/swig/pull/460

> plplot 5.11.0 is building fine in Rawhide with a patched swig 3.0.6, octave 
> 4.0.0, and the patch to plplot for swig 3.0.6 doc issue.

Hi Orion:

Thanks for that encouraging news with regard to good builds of the
octave binding of PLplot against Octave-4.0.0.  But I have also been
concerned about the run-time results as well which you can
straightforwardly check there by simply running

cmake .... >& cmake.out
make test_diff_psc >& test_diff_psc.out

in an initially empty build tree.

Normally that test shows there are no differences between the
octave-generated and C-generated results for all our examples for the
Octave-3.x.y case.  If running that test there shows the same thing
for the Octave-4.0.0 case that is a very strong test of our octave
bindings for that case.

Regardless of whether you try such a run time check, your build
success motivates me to expand the epa_build implementation to see how
far I can get with an epa_build of Octave-4.0.0 and patched versions
of swig-2 and swig-3.  Assuming I can epa_build all of those, then
that would allow me to do the above run-time check here for patched
versions of both swig-2 and swig-3, and thus help build the case to
get your swig patch (or two variants of that if your patch has to be
modified for swig-2) into the next official releases of both swig-2
and swig-3.

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
__________________________

Re: [Plplot-devel] Octave 4.0.0

[Orion P. <or...@co...>]

On 07/10/2015 12:04 PM, Orion Poplawski wrote:
>
> My fix for octave 4.0,0 support in swig is here:
>
> https://github.com/swig/swig/pull/460
>
> I'll test builds of plplot once the swig build is complete.

plplot 5.11.0 is building fine in Rawhide with a patched swig 3.0.6, 
octave 4.0.0, and the patch to plplot for swig 3.0.6 doc issue.

http://koji.fedoraproject.org/koji/taskinfo?taskID=10334481


-- 
Orion Poplawski
Technical Manager                     303-415-9701 x222
NWRA/CoRA Division                    FAX: 303-415-9702
3380 Mitchell Lane                  or...@co...
Boulder, CO 80301              http://www.cora.nwra.com

[Plplot-devel] The CMake minimum version has been bumped

[Alan W. I. <ir...@be...>]

I have just (dd9f79e) bumped the minimum version of CMake from 3.2.2
to 3.2.3 for all platforms other than Linux and Cygwin (where the
minimum version remains at 3.0.1).  The motivation for this change has
been given in the dd9f79e commit message.  I recommend hose using the
"MinGW Makefiles" generator and mingw32-make should pay especially
close attention to that commit message and the references within it.

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
__________________________

Re: [Plplot-devel] Comprehensive testing on Cygwin with Tcl/Tk/Itcl/Itk

[Alan W. I. <ir...@be...>]

Hi Arjen:

In response to your previous report of the full test with octave where
ctest failed virtually silently, I have tried to reproduce that
lack of information in ctest.out here by running a slightly
modified version of the script which moves
plplot_octave.oct to a different directory after it is built,
but instead for that case I got full error message from ctest.out, i.e.,

5: Test command: /bin/bash "-c" "EXAMPLES_DIR=/home/software/plplot/HEAD/comprehensive_test_disposeable/shared/build_tree/examples SRC_EXAMP
LES_DIR=/home/software/plplot/HEAD/plplot.git/examples OUTPUT_DIR=/home/software/plplot/HEAD/comprehensive_test_disposeable/shared/build_tre
e/ctest_examples_output_dir VC_CTEST_DIRECTORY= ./plplot-test.sh --verbose --device=psc --front-end=octave"
5: Test timeout computed to be: 1500
5: Testing front-end octave
5: /home/software/plplot/HEAD/comprehensive_test_disposeable/shared/build_tree/plplot_test/..
5: error: `plplot_octave' undefined near line 4 column 1
5: error: called from:
5: error:   /home/software/plplot/HEAD/comprehensive_test_disposeable/shared/build_tree/examples/../bindings/octave/plplot_stub.m at line 4, column 1
  2/26 Test  #5: examples_octave ..................***Failed    0.20 sec

So I am going to ascribe that lack of error messages in your case to some
subtle stderr or stdout bug in octave, bash, or ctest on Cygwin. Until
that is fixed, I suggest that if an "empty" ctest error message is
encountered on Cygwin, it is best to temporarily avoid that test as
you have done for your latest report below.

On 2015-07-10 07:18-0000 Arjen Markus wrote:

> The tarball indicates that the command "plplot_octave" was not
found. Could it be that the subdirectory "dll" needs to be added to
the LD_LIBRARY_PATH environment variable or perhaps to the PATH
variable? I have not spent that much time on figuring this out -
running the examples by hand was unsuccessful in a completely
different way, but that is my ignorance regarding Octave (complaints
about x00c not being the function file name "").

Thanks for that new report, and I agree with your analysis that octave
is looking in the wrong directory for plplot_octave.oct.  I believe I
have now fixed that issue (commit d645c88) so please try again.

Notice the d645c88 commit message includes a really simple test
(adapted from bindings/octave/USAGE) of the octave binding of PLplot
in the build tree that I did in addition to the comprehensive test
that I did of my change.  However, that simple test is an interactive
test (using -dev xwin) so will only work for you once you get your X
problems caused by the octave package install straightened out.

By the way, from his report it appears Greg has not encountered those
X problems even though he has installed octave.  And both his hardware
and Cygwin version are 64-bit just the same as your case. So the
"obvious" conclusion is you two should get identical comprehensive
test results, but so far that is not the case.

Instead, you have a weird thing going on with Octave and X on Cygwin, and he
is possibly (depending on your answer to my previous post) having a
weird thing going on with pysol and python compatibility on Cygwin.

I encourage you guys and Phil to pool your Cygwin expertise so you can
all learn how to avoid these weird problems that are interfering
with obtaining the best comprehensive tests on that platform.

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
__________________________

[Plplot-devel] What exact numpy package have you currently got installed on Cygwin for your comprehensive testing?

[Alan W. I. <ir...@be...>]

Hi Arjen:

I have been helping Greg Jung off list with reproducing your best
Cygwin comprehensive test results so far, and he is pretty close, but
he is having trouble with inconsistencies between various Cygwin numpy
packages he installs and the Cygwin development package for
python-2.7.10 that you both use for comprehensive testing.

So it would be a big help to him if you answered the question in
the subject 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
__________________________

Re: [Plplot-devel] Would you be willing to test PLplot against Octave-3.8.2 or later in the 3.8 series?

[Alan W. I. <ir...@be...>]

On 2015-07-10 23:27+0100 Andrew Ross wrote:

>
> I've built and run the non-interactive octave tests and they complete with
> no errors using octave-3.8.2 on Ubuntu 15.04 (vivid). I did have some
> build errors, but that was just related to the hdf5.h header being in a
> new location.

Hi Andrew:

The current status of the Cygwin octave-3.8.2 issue is
Arjen discovered the problem was an assumption in our scripts
concerning the location of the plplot_octave.oct dll for the Windows
case, and I am in the middle of fixing that assumption.

However, once I get that fix done, if Arjen runs into additional issues
it is good to know that PLplot basically works for octave-3.8.2
so many thanks for proving that.

With regard to the hdf5.h location issue you discovered on Ubuntu,
could you please make the required small adjustment to
cmake/modules/octave.cmake using PATH_SUFFIXES on the find_path
command so that it finds hdf5.h preferentially in the traditional
location (/usr/include/hdf5.h), but if it is not found there it looks
in the subdirectory of that location which is appropriate for Ubuntu
(and probably also later versions of Debian than I have at the
moment).

Thanks in advance for this small fix.

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
__________________________

Re: [Plplot-devel] Comprehensive testing on MinGW/MSYS

[Alan W. I. <ir...@be...>]

On 2015-07-10 09:06-0000 Arjen Markus wrote:

> Hi Alan,

> As I wrote to Walt, I had to fix the logic for inclusion of
"unistd.h" for the MinGW/MSYS platform, but it worked fine. The logic
is far simpler than what we had before. The tarball shows a limited
but otherwise perfect result.

Hi Arjen:

Thanks for fixing that issue and also for the perfect "MSYS Makefiles"
report for the noninteractive case.

While I am working on the octave issue you turned up for Cygwin, would
you be willing also to run the script in the noninteractive mode
(since that is so easy compared to interactive comprehensive tests)
for one other platform as well?  In particular it would be great to
see your noninteractive comprehensive test results for the
MinGW-w64/MSYS2 platform.

The reason I am keen that we support this platform (however, _only_
the vanilla version you get by running the MSYS2 install documented at
<http://sourceforge.net/p/msys2/wiki/Home/>) is because MSYS2 has a
very large and also rapidly growing popularity, automatically delivers
the same PLplot prerequisites that are available from Cygwin, 
automatically delivers all the platform bug fixes (e.g., parallel
builds are possible!) that are made for Cygwin, and (like MSYS) does
not have the Cygwin baggage (our libraries and applications will be
built natively, i.e., with no link to a big dll such as cygwin.dll).

Therefore, I hope you are willing to run the comprehensive test script
for this platform not only to potentially help Walt but potentially
many others as well who are keen on this platform.

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
__________________________

Re: [Plplot-devel] Would you be willing to test PLplot against Octave-3.8.2 or later in the 3.8 series?

[Andrew R. <and...@us...>]

I've built and run the non-interactive octave tests and they complete with
no errors using octave-3.8.2 on Ubuntu 15.04 (vivid). I did have some
build errors, but that was just related to the hdf5.h header being in a
new location. 

Regards

Andrew

On Fri, Jul 10, 2015 at 09:48:54PM +0100, Andrew Ross wrote:
> 
> Coincidentally I have just this week upgraded my Ubuntu install so I now
> have octave 3.8.2. I will run some tests and see what happens.
> 
> Andre
> 
> On Thu, Jul 09, 2015 at 03:01:53AM -0700, Alan Irwin wrote:
> > Hi Andrew:
> > 
> > In case you didn't have a chance to read it, the summary of the recent
> > part of my thread with Arjen is he now has a successful build on
> > Cygwin of our octave bindings against Octave-3.8.2.  However, he
> > discovered there were run-time errors when running our octave examples
> > for that version of Octave. I do not get those run-time errors for the
> > Octave-3.6.2 Linux case.
> > 
> > Would you be willing to test PLplot against Octave-3.8.2 or later
> > yourself to see if the issue Arjen is seeing is confined to
> > just Cygwin?
> > 
> > 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
> > __________________________
> 
> ------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
> _______________________________________________
> Plplot-devel mailing list
> Plp...@li...
> https://lists.sourceforge.net/lists/listinfo/plplot-devel

Re: [Plplot-devel] Would you be willing to test PLplot against Octave-3.8.2 or later in the 3.8 series?

[Andrew R. <and...@us...>]

Coincidentally I have just this week upgraded my Ubuntu install so I now
have octave 3.8.2. I will run some tests and see what happens.

Andre

On Thu, Jul 09, 2015 at 03:01:53AM -0700, Alan Irwin wrote:
> Hi Andrew:
> 
> In case you didn't have a chance to read it, the summary of the recent
> part of my thread with Arjen is he now has a successful build on
> Cygwin of our octave bindings against Octave-3.8.2.  However, he
> discovered there were run-time errors when running our octave examples
> for that version of Octave. I do not get those run-time errors for the
> Octave-3.6.2 Linux case.
> 
> Would you be willing to test PLplot against Octave-3.8.2 or later
> yourself to see if the issue Arjen is seeing is confined to
> just Cygwin?
> 
> 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
> __________________________

Re: [Plplot-devel] Octave 4.0.0

[Orion P. <or...@co...>]

On 07/08/2015 03:36 PM, Alan W. Irwin wrote:
> On 2015-07-08 15:46-0000 Arjen Markus wrote:
> 
>> Well, I tried it with Octave allowed, but I get build errors - see
> the tarball. It does not seem to be complaining about 2 versus 4
> arguments anymore, but something is definitely wrong. Could that be
> the SWIG version? (Note: I did not use the very latest checkout, but
> the commits I saw have nothing to do with Octave).
> 
> To Arjen and Orion:
> 
> @Arjen:
> Thanks for this comprehensive test report.
> 
> The short response for working around the octave error you
> encountered is you should remove the Cygwin package
> octave-devel-4.0.0-1 and install instead octave-devel-3.8.2-1. (And
> you should also confirm you have libhdf5-devel-1.8.15-1 installed.)
> And then you should try the test again (probably it is best if you do
> that with the PLplot master tip version).  I am pretty sure that
> will "just work" since the 2 versus 4 argument issue has now been fixed
> and we have plenty of good tests of octave-3 on other platforms.
> 
> @Orion:
> 
> I suggest you also use Octave-3 for now assuming that Fedora has
> Octave-3 packages.
> 
> @Arjen:
> 
> Here is my longer response to your report.
> 
> It turns out you ran into virtually exactly the same octave problems
> that Orion reported here so you may want to reread his recent post
> about this and my response to it.
> 
> The first part of Orion's post shows that the swig-3.0.6
> octave component does not like leading blanks in documentation of the
> swig-generated bindings for some reason, but swig-3.0.5 is OK with
> that. I have fixed that issue as of the current master tip.  Your use
> of ae0e9da misses that fix to our documentation of the swig-generated
> bindings, but missing that fix did not matter for your case since
> Cygwin currently supplies you with swig-3.0.5.
> 
> However, once Orion locally fixed the leading blank issue in our
> documentation of swig-generated bindings (the issue that is now
> permanently fixed in master tip), he went on to describe additional
> issues with octave #includes supplied by swig that are not compatible
> with Octave-4.0.0, and it appears you ran into those exact same
> swig issues.
> 
> In sum, it appears build issues like you encountered above will not allow us
> to even try Octave-4.0.0 until swig fixes their Octave-4.0.0
> #include issues, and that swig fix propagates to swig versions we are
> using.  So for now (commit id 2ad5aef) the build system issues a
> WARNING if it finds Octave-4.  For that case it disables the octave
> bindings unless the user specifically opts in using the cmake
> experimental option -DTRY_OCTAVE4=ON.
> 
> Once swig fixes their problem with Octave-4 #includes so that
> -DTRY_OCTAVE4=ON has even a chance of working, I assume we will have a
> lot of work ahead of us both in the octave bindings and octave
> examples to become compatible with Octave-4.  So I expect
> -DTRY_OCTAVE4=ON will be experimental for quite some time after the
> required swig fix.
> 
> Alan
> __________________________
> Alan W. Irwin

My fix for octave 4.0,0 support in swig is here:

https://github.com/swig/swig/pull/460

I'll test builds of plplot once the swig build is complete.


-- 
Orion Poplawski
Technical Manager                     303-415-9701 x222
NWRA, Boulder/CoRA Office             FAX: 303-415-9702
3380 Mitchell Lane                       or...@nw...
Boulder, CO 80301                   http://www.nwra.com

[Plplot-devel] Comprehensive testing on MinGW/MSYS

[Arjen M. <Arj...@de...>]

Hi Alan,



As I wrote to Walt, I had to fix the logic for inclusion of "unistd.h" for the MinGW/MSYS platform, but it worked fine. The logic is far simpler than what we had before. The tarball shows a limited but otherwise perfect result.



Regards,



Arjen


DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail.

Re: [Plplot-devel] Comprehensive testing on Cygwin with Tcl/Tk/Itcl/Itk

[Arjen M. <Arj...@de...>]

Hi Alan,



The tarball indicates that the command "plplot_octave" was not found. Could it be that the subdirectory "dll" needs to be added to the LD_LIBRARY_PATH environment variable or perhaps to the PATH variable? I have not spent that much time on figuring this out - running the examples by hand was unsuccessful in a completely different way, but that is my ignorance regarding Octave (complaints about x00c not being the function file name "").



Regards,



Arjen



From: Arjen Markus [mailto:Arj...@de...]
Sent: Friday, July 10, 2015 8:41 AM
To: plp...@li...
Subject: Re: [Plplot-devel] Comprehensive testing on Cygwin with Tcl/Tk/Itcl/Itk


Hi Alan,

> -----Original Message-----
> From: Alan W. Irwin [mailto:ir...@be...]
> Sent: Thursday, July 09, 2015 10:30 AM
> To: Arjen Markus; Orion Poplawski
> Cc: plp...@li...
> Subject: RE: [Plplot-devel] Comprehensive testing on Cygwin with Tcl/Tk/Itcl/Itk
>
> Hi Arjen:
>
> First a comment about your Cygwin setup.
>
> The cmake.out file revealed (as you mentioned in your first message) that you are
> having trouble with X.  That sounds like exactly the same problem that you
> intermittently had before.  Is it possible installation of _any_ software on Cygwin
> means you have to go through the whole X initialization procedure again? And if that
> proves to be the case I hope you can automate that procedure so these intermittent
> troubles with X disappear.
>
No, my script to start the comprehensive tests first starts the X Window server. When I leave out Octave, it all goes well, but with Octave I see that CMake does not continue after printing where it found Octave. I suspect something is waiting for input, but I do not yet have a clue what. As yesterday was my day to travel home, I did not have an opportunity to dig into it. So, instead I tried it without the X server running - this was just a lucky guess. And then I ran into the ctest problems.

> On 2015-07-09 05:42-0000 Arjen Markus wrote:
>
> > The Octave tests failed in the ctest step as you can see in the
> tarball. I have not found any indication as to why to it failed though.
>
> Thanks for that report.
>
> The cmake.out results for finding Octave-3 look good.
> And it appears there was no build error on Cygwin with our
> Octave(-3) binding enabled which is good.
>
> Of course, as you stated there is an obvious run-time error with Octave on that
> platform, and ctest is not very informative about the details of that error.  So I
> suggest you add the script options
>
> --do_ctest no --build_command "make"
>
> which will skip the uninformative ctest phase and also keep the build non-parallel
> when building the test_noninteractive target (which is the first thing done by the
> comprehensive test script if ctest is skipped).
>
> When the comprehensive test script builds that target it should run into the same
> octave run-time errors as ctest only it will do that verbosely and also in a non-parallel
> way which will show up in the report tarball to help me to diagnose exactly what is
> wrong with the octave component on Cygwin.
>
Okay, that is quite doable.  I will start the tests that way rightaway.

Regards,

Arjen


DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail.
DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail.

Re: [Plplot-devel] Comprehensive testing on Cygwin with Tcl/Tk/Itcl/Itk

[Arjen M. <Arj...@de...>]

Hi Alan,

> -----Original Message-----
> From: Alan W. Irwin [mailto:ir...@be...]
> Sent: Thursday, July 09, 2015 10:30 AM
> To: Arjen Markus; Orion Poplawski
> Cc: plp...@li...
> Subject: RE: [Plplot-devel] Comprehensive testing on Cygwin with Tcl/Tk/Itcl/Itk
>
> Hi Arjen:
>
> First a comment about your Cygwin setup.
>
> The cmake.out file revealed (as you mentioned in your first message) that you are
> having trouble with X.  That sounds like exactly the same problem that you
> intermittently had before.  Is it possible installation of _any_ software on Cygwin
> means you have to go through the whole X initialization procedure again? And if that
> proves to be the case I hope you can automate that procedure so these intermittent
> troubles with X disappear.
>
No, my script to start the comprehensive tests first starts the X Window server. When I leave out Octave, it all goes well, but with Octave I see that CMake does not continue after printing where it found Octave. I suspect something is waiting for input, but I do not yet have a clue what. As yesterday was my day to travel home, I did not have an opportunity to dig into it. So, instead I tried it without the X server running - this was just a lucky guess. And then I ran into the ctest problems.

> On 2015-07-09 05:42-0000 Arjen Markus wrote:
>
> > The Octave tests failed in the ctest step as you can see in the
> tarball. I have not found any indication as to why to it failed though.
>
> Thanks for that report.
>
> The cmake.out results for finding Octave-3 look good.
> And it appears there was no build error on Cygwin with our
> Octave(-3) binding enabled which is good.
>
> Of course, as you stated there is an obvious run-time error with Octave on that
> platform, and ctest is not very informative about the details of that error.  So I
> suggest you add the script options
>
> --do_ctest no --build_command "make"
>
> which will skip the uninformative ctest phase and also keep the build non-parallel
> when building the test_noninteractive target (which is the first thing done by the
> comprehensive test script if ctest is skipped).
>
> When the comprehensive test script builds that target it should run into the same
> octave run-time errors as ctest only it will do that verbosely and also in a non-parallel
> way which will show up in the report tarball to help me to diagnose exactly what is
> wrong with the octave component on Cygwin.
>
Okay, that is quite doable.  I will start the tests that way rightaway.

Regards,

Arjen



DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail.

[Plplot-devel] Would you be willing to test PLplot against Octave-3.8.2 or later in the 3.8 series?

[Alan W. I. <ir...@be...>]

Hi Andrew:

In case you didn't have a chance to read it, the summary of the recent
part of my thread with Arjen is he now has a successful build on
Cygwin of our octave bindings against Octave-3.8.2.  However, he
discovered there were run-time errors when running our octave examples
for that version of Octave. I do not get those run-time errors for the
Octave-3.6.2 Linux case.

Would you be willing to test PLplot against Octave-3.8.2 or later
yourself to see if the issue Arjen is seeing is confined to
just Cygwin?

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
__________________________

Re: [Plplot-devel] Comprehensive testing on Cygwin with Tcl/Tk/Itcl/Itk

[Alan W. I. <ir...@be...>]

Hi Arjen:

First a comment about your Cygwin setup.

The cmake.out file revealed (as you mentioned in your first message) that
you are having trouble with X.  That sounds like exactly the same
problem that you intermittently had before.  Is it possible
installation of _any_ software on Cygwin means you have to go through
the whole X initialization procedure again? And if that proves to be
the case I hope you can automate that procedure so these intermittent
troubles with X disappear.

On 2015-07-09 05:42-0000 Arjen Markus wrote:

> The Octave tests failed in the ctest step as you can see in the
tarball. I have not found any indication as to why to it failed
though.

Thanks for that report.

The cmake.out results for finding Octave-3 look good.
And it appears there was no build error on Cygwin with our
Octave(-3) binding enabled which is good.

Of course, as you stated there is an obvious run-time error with
Octave on that platform, and ctest is not very informative about the
details of that error.  So I suggest you add the script options

--do_ctest no --build_command "make"

which will skip the uninformative ctest phase and also keep the build
non-parallel when building the test_noninteractive target (which is
the first thing done by the comprehensive test script if ctest is
skipped).

When the comprehensive test script builds that target it should run
into the same octave run-time errors as ctest only it will do that
verbosely and also in a non-parallel way which will show up in the
report tarball to help me to diagnose exactly what is wrong with the
octave component on Cygwin.

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
__________________________

Re: [Plplot-devel] Comprehensive testing on Cygwin with Tcl/Tk/Itcl/Itk

[Arjen M. <Arj...@de...>]

Hi Alan,



The Octave tests failed in the ctest step as you can see in the tarball. I have not found any indication as to why to it failed though.



Regards,



Arjen

From: Arjen Markus [mailto:Arj...@de...]
Sent: Thursday, July 09, 2015 7:12 Am
To: Alan W. Irwin; Orion Poplawski
Cc: plp...@li...
Subject: Re: [Plplot-devel] Comprehensive testing on Cygwin with Tcl/Tk/Itcl/Itk


Hi Alan,



I uninstalled Octave 4 and installed 3.8, but when I ran the comprehensive test script, it got stuck somehow in the Cmake step, when it came to Octave. It did not advance for several minutes, so I broke it off. I then tried the ordinary Cmake and Make steps - without the X Window server as it happened - and that worked. Now I am running the comprehensive tests without X and it all seems to be going fine. More later, but there seems to be something in the octave-X connection which is hindering the automatic testing. Could be that it wants me to click in the X window, but I did not see anything specific, so that is something to look into later.



Regards,



Arjen



> -----Original Message-----
> From: Alan W. Irwin [mailto:ir...@be...]
> Sent: Wednesday, July 08, 2015 11:37 PM
> To: Arjen Markus; Orion Poplawski
> Cc: plp...@li...
> Subject: RE: [Plplot-devel] Comprehensive testing on Cygwin with Tcl/Tk/Itcl/Itk
>
> On 2015-07-08 15:46-0000 Arjen Markus wrote:
>
> > Well, I tried it with Octave allowed, but I get build errors - see
> the tarball. It does not seem to be complaining about 2 versus 4 arguments anymore,
> but something is definitely wrong. Could that be the SWIG version? (Note: I did not
> use the very latest checkout, but the commits I saw have nothing to do with Octave).
>
> To Arjen and Orion:
>
> @Arjen:
> Thanks for this comprehensive test report.
>
> The short response for working around the octave error you encountered is you
> should remove the Cygwin package
> octave-devel-4.0.0-1 and install instead octave-devel-3.8.2-1. (And you should also
> confirm you have libhdf5-devel-1.8.15-1 installed.) And then you should try the test
> again (probably it is best if you do that with the PLplot master tip version).  I am
> pretty sure that will "just work" since the 2 versus 4 argument issue has now been
> fixed and we have plenty of good tests of octave-3 on other platforms.
>
> @Orion:
>
> I suggest you also use Octave-3 for now assuming that Fedora has
> Octave-3 packages.
>
> @Arjen:
>
> Here is my longer response to your report.
>
> It turns out you ran into virtually exactly the same octave problems that Orion
> reported here so you may want to reread his recent post about this and my response
> to it.
>
> The first part of Orion's post shows that the swig-3.0.6 octave component does not
> like leading blanks in documentation of the swig-generated bindings for some reason,
> but swig-3.0.5 is OK with that. I have fixed that issue as of the current master tip.
> Your use of ae0e9da misses that fix to our documentation of the swig-generated
> bindings, but missing that fix did not matter for your case since Cygwin currently
> supplies you with swig-3.0.5.
>
> However, once Orion locally fixed the leading blank issue in our documentation of
> swig-generated bindings (the issue that is now permanently fixed in master tip), he
> went on to describe additional issues with octave #includes supplied by swig that are
> not compatible with Octave-4.0.0, and it appears you ran into those exact same swig
> issues.
>
> In sum, it appears build issues like you encountered above will not allow us to even
> try Octave-4.0.0 until swig fixes their Octave-4.0.0 #include issues, and that swig fix
> propagates to swig versions we are using.  So for now (commit id 2ad5aef) the build
> system issues a WARNING if it finds Octave-4.  For that case it disables the octave
> bindings unless the user specifically opts in using the cmake experimental option -
> DTRY_OCTAVE4=ON.
>
> Once swig fixes their problem with Octave-4 #includes so that -
> DTRY_OCTAVE4=ON has even a chance of working, I assume we will have a lot of
> work ahead of us both in the octave bindings and octave examples to become
> compatible with Octave-4.  So I expect -DTRY_OCTAVE4=ON will be experimental
> for quite some time after the required swig fix.
>
> 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
> __________________________
DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail.
DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail.

Re: [Plplot-devel] Comprehensive testing on Cygwin with Tcl/Tk/Itcl/Itk

[Arjen M. <Arj...@de...>]

Hi Alan,



I uninstalled Octave 4 and installed 3.8, but when I ran the comprehensive test script, it got stuck somehow in the Cmake step, when it came to Octave. It did not advance for several minutes, so I broke it off. I then tried the ordinary Cmake and Make steps - without the X Window server as it happened - and that worked. Now I am running the comprehensive tests without X and it all seems to be going fine. More later, but there seems to be something in the octave-X connection which is hindering the automatic testing. Could be that it wants me to click in the X window, but I did not see anything specific, so that is something to look into later.



Regards,



Arjen



> -----Original Message-----
> From: Alan W. Irwin [mailto:ir...@be...]
> Sent: Wednesday, July 08, 2015 11:37 PM
> To: Arjen Markus; Orion Poplawski
> Cc: plp...@li...
> Subject: RE: [Plplot-devel] Comprehensive testing on Cygwin with Tcl/Tk/Itcl/Itk
>
> On 2015-07-08 15:46-0000 Arjen Markus wrote:
>
> > Well, I tried it with Octave allowed, but I get build errors - see
> the tarball. It does not seem to be complaining about 2 versus 4 arguments anymore,
> but something is definitely wrong. Could that be the SWIG version? (Note: I did not
> use the very latest checkout, but the commits I saw have nothing to do with Octave).
>
> To Arjen and Orion:
>
> @Arjen:
> Thanks for this comprehensive test report.
>
> The short response for working around the octave error you encountered is you
> should remove the Cygwin package
> octave-devel-4.0.0-1 and install instead octave-devel-3.8.2-1. (And you should also
> confirm you have libhdf5-devel-1.8.15-1 installed.) And then you should try the test
> again (probably it is best if you do that with the PLplot master tip version).  I am
> pretty sure that will "just work" since the 2 versus 4 argument issue has now been
> fixed and we have plenty of good tests of octave-3 on other platforms.
>
> @Orion:
>
> I suggest you also use Octave-3 for now assuming that Fedora has
> Octave-3 packages.
>
> @Arjen:
>
> Here is my longer response to your report.
>
> It turns out you ran into virtually exactly the same octave problems that Orion
> reported here so you may want to reread his recent post about this and my response
> to it.
>
> The first part of Orion's post shows that the swig-3.0.6 octave component does not
> like leading blanks in documentation of the swig-generated bindings for some reason,
> but swig-3.0.5 is OK with that. I have fixed that issue as of the current master tip.
> Your use of ae0e9da misses that fix to our documentation of the swig-generated
> bindings, but missing that fix did not matter for your case since Cygwin currently
> supplies you with swig-3.0.5.
>
> However, once Orion locally fixed the leading blank issue in our documentation of
> swig-generated bindings (the issue that is now permanently fixed in master tip), he
> went on to describe additional issues with octave #includes supplied by swig that are
> not compatible with Octave-4.0.0, and it appears you ran into those exact same swig
> issues.
>
> In sum, it appears build issues like you encountered above will not allow us to even
> try Octave-4.0.0 until swig fixes their Octave-4.0.0 #include issues, and that swig fix
> propagates to swig versions we are using.  So for now (commit id 2ad5aef) the build
> system issues a WARNING if it finds Octave-4.  For that case it disables the octave
> bindings unless the user specifically opts in using the cmake experimental option -
> DTRY_OCTAVE4=ON.
>
> Once swig fixes their problem with Octave-4 #includes so that -
> DTRY_OCTAVE4=ON has even a chance of working, I assume we will have a lot of
> work ahead of us both in the octave bindings and octave examples to become
> compatible with Octave-4.  So I expect -DTRY_OCTAVE4=ON will be experimental
> for quite some time after the required swig fix.
>
> 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
> __________________________

DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail.

Re: [Plplot-devel] Comprehensive testing on Cygwin with Tcl/Tk/Itcl/Itk

[Alan W. I. <ir...@be...>]

On 2015-07-08 14:36-0700 Alan W. Irwin wrote:

> In sum, it appears build issues like you encountered above will not
> allow us to even try Octave-4.0.0 until swig fixes their Octave-4.0.0
> #include issues, and that swig fix propagates to swig versions we are
> using.  So for now (commit id 2ad5aef) the build system issues a
> WARNING if it finds Octave-4.  For that case it disables the octave
> bindings unless the user specifically opts in using the cmake
> experimental option -DTRY_OCTAVE4=ON.

Note that commit id 2ad5aef had a bug ("3." was used for an
Octave version comparison check rather than "4.") which is addressed
in commit 0f72310.

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
__________________________

Re: [Plplot-devel] Comprehensive testing on Cygwin with Tcl/Tk/Itcl/Itk

[Alan W. I. <ir...@be...>]

On 2015-07-08 15:46-0000 Arjen Markus wrote:

> Well, I tried it with Octave allowed, but I get build errors - see
the tarball. It does not seem to be complaining about 2 versus 4
arguments anymore, but something is definitely wrong. Could that be
the SWIG version? (Note: I did not use the very latest checkout, but
the commits I saw have nothing to do with Octave).

To Arjen and Orion:

@Arjen:
Thanks for this comprehensive test report.

The short response for working around the octave error you
encountered is you should remove the Cygwin package
octave-devel-4.0.0-1 and install instead octave-devel-3.8.2-1. (And
you should also confirm you have libhdf5-devel-1.8.15-1 installed.)
And then you should try the test again (probably it is best if you do
that with the PLplot master tip version).  I am pretty sure that
will "just work" since the 2 versus 4 argument issue has now been fixed
and we have plenty of good tests of octave-3 on other platforms.

@Orion:

I suggest you also use Octave-3 for now assuming that Fedora has
Octave-3 packages.

@Arjen:

Here is my longer response to your report.

It turns out you ran into virtually exactly the same octave problems
that Orion reported here so you may want to reread his recent post
about this and my response to it.

The first part of Orion's post shows that the swig-3.0.6
octave component does not like leading blanks in documentation of the
swig-generated bindings for some reason, but swig-3.0.5 is OK with
that. I have fixed that issue as of the current master tip.  Your use
of ae0e9da misses that fix to our documentation of the swig-generated
bindings, but missing that fix did not matter for your case since
Cygwin currently supplies you with swig-3.0.5.

However, once Orion locally fixed the leading blank issue in our
documentation of swig-generated bindings (the issue that is now
permanently fixed in master tip), he went on to describe additional
issues with octave #includes supplied by swig that are not compatible
with Octave-4.0.0, and it appears you ran into those exact same
swig issues.

In sum, it appears build issues like you encountered above will not 
allow us to even try Octave-4.0.0 until swig fixes their Octave-4.0.0
#include issues, and that swig fix propagates to swig versions we are
using.  So for now (commit id 2ad5aef) the build system issues a
WARNING if it finds Octave-4.  For that case it disables the octave
bindings unless the user specifically opts in using the cmake
experimental option -DTRY_OCTAVE4=ON.

Once swig fixes their problem with Octave-4 #includes so that
-DTRY_OCTAVE4=ON has even a chance of working, I assume we will have a
lot of work ahead of us both in the octave bindings and octave
examples to become compatible with Octave-4.  So I expect
-DTRY_OCTAVE4=ON will be experimental for quite some time after the
required swig fix.

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
__________________________

Re: [Plplot-devel] Comprehensive testing on Cygwin with Tcl/Tk/Itcl/Itk

[Arjen M. <Arj...@de...>]

Hi Alan,



Well, I tried it with Octave allowed, but I get build errors - see the tarball. It does not seem to be complaining about 2 versus 4 arguments anymore, but something is definitely wrong. Could that be the SWIG version? (Note: I did not use the very latest checkout, but the commits I saw have nothing to do with Octave).



Regards,



Arjen



> -----Original Message-----
> From: Alan W. Irwin [mailto:ir...@be...]
> Sent: Tuesday, July 07, 2015 9:21 PM
> To: Arjen Markus
> Cc: plp...@li...
> Subject: RE: [Plplot-devel] Comprehensive testing on Cygwin with Tcl/Tk/Itcl/Itk
>
> On 2015-07-07 05:53-0000 Arjen Markus wrote:
>
> > Well, that was spot on :). See the attached tarball. The test script completed
> without any complaints and the comparisons are clean.
>
> Hi Arjen:
>
> I agree with your conclusions about the the clean nature of these results for the
> largest number of PLplot components tested on Cygwin so far.  My thanks for your
> essential help in achieving this high point for Cygwin!
>
> That said, your report does indicate there is still one noninteractive issue that we
> should deal with for this release cycle, and my apologies for missing it until now.
> Your latest result uses
>
> cmake_added_options=-DENABLE_octave=OFF -DENABLE_ada=OFF
>
> to workaround some build system issues on the Cygwin platform.
> -DENABLE_octave=OFF is something you adopted on June 3rd after installing the
> final Octave-related Cygwin package that was required.  Your comment back then
> was
>
> -        Allowing Octave gave Cmake errors about two versus four
> arguments. I turned that off.
>
> As far as I know we never followed up further on this build-system issue for
> configuring the Octave binding of PLplot, but I would like to do that now.
>
> So when you get a change could you run the script again without -
> DENABLE_octave=OFF so I can diagnose (and hopefully fix) this issue?
>
> I believe this issue will be the last noninteractive one I will attempt to deal with for the
> Cygwin platform in this release cycle.
> Of course, you also use -DENABLE_ada=OFF to workaround the well-known Ada
> language support issue on Cygwin, but I expect you will be continuing with that
> workaround indefinitely because it is likely I will only be able to deal with this issue
> some time after the planned
> 5.11.1 release.
>
> 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
> __________________________

DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail.