plplot-devel

[Plplot-devel] Comprehensive testing

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

This is directly not only to Arjen, but also to everybody else here who
wants to help out with comprehensive testing for this release.

On 2016-12-13 11:49-0000 Arjen Markus wrote:

> Hi Alan,
>
>
>
>> -----Original Message-----
>> From: Alan W. Irwin [mailto:ir...@be...]
>> Sent: Tuesday, December 13, 2016 12:13 PM
>>
>> I am very happy to hear that.  Big sigh of relief!
>>
>> Since I currently have comprehensive test success on Linux and you now also have
>> that on Cygwin, would you be willing to follow up with a comprehensive test on
>> MinGW-w64/MSYS2 and your spot checks on MSVC with ifort?
>>
> Sure, that should be no particular problem.
>

@Arjen:

Great.

I should have emphasized you should drop all constraints for these
comprehensive tests other than the ones that have
proved absolutely necessary in the past for the given platform.

So ideally your script launch (aside from the nice part, see below)
should be

scripts/comprehensive_test.sh --do_submit_dashboard yes --do_test_interactive no

with very few if any further constraining options.

@Everybody:

I have specified the

--do_submit_dashboard yes

option here.  For a normally unconstrained comprehensive test on a given
platform, that will submit 3 separate dashboards (for the ctest
results for the shared + dynamic devices case, the shared + nondynamic
devices case, and the static + nondynamic devices case), and you
should be able to see that subset of the comprehensive test results at
<http://my.cdash.org/index.php?project=PLplot_git>.  But I ask you to
also send me the report tarball as well (normally stored at
../comprehensive_test_disposeable/comprehensive_test.tar.gz) both when
the script fails to complete (so I can help you figure out the problem
or disable the non-working parts of PLplot on your platform so the
script completes) and when the script completes (so I can summarize
your complete results with your permission at
<https://sourceforge.net/p/plplot/wiki/Testing_PLplot/#Testing@20Reports>).

I presume most testers here do want to skip the interactive part of
the comprehensive tests because X is so slow on Cygwin, and if you do
decide to go ahead with the interactive part of the tests on platforms
where X is fast, then I should warn you there is a whole lot of
keyboarding and mouse clicking to get through to finish the
interactive part of the comprehensive test.  For myself, I tend
to use

--do_test_interactive no

a lot for these reasons, but I do drop this option (or specify the
equivalent --do_test_interactive yes) several times during a release
cycle to make sure the interactive part of PLplot is working properly.
But very few others need to put themselves through that boredom unless
and until they are highly motivated to test PLplot interactive
capability on their particular platform.

@Arjen:

This request for more comprehensive tests is for both
MinGW-w64/MSYS2 and Cygwin (since the successful test you completed
just now for that platform was constrained just to be the build-tree
ctest test for the shared library + dynamic devices case).

These requested comprehensive tests should be pretty straightforward
for you to do since your launch script where you specify the platform
setup (set environment variables, etc. and the comprehensive test options)
should be completely automated by now in the interest of repeatability.
So all you should really have to do is sit back and let your computer do all
the work.

@Everybody:

A tip for Unix users here is to run these comprehensive
tests as follows

time (nice -19 scripts/comprehensive_test.sh --do_submit_dashboard yes --do_test_interactive no )

The time part of this lets you know how much time this took once the
command finishes.  The nice -19 part forces this comprehensive test to
only use the cpu if you don't need it for something else.  So when I
do the above, my computer feels somewhat slower (because of all the
disk i/o going on with these tests and the mememory used by these
tests), but the computer is still quite usable.  If I don't specify
nice as above, then the computer seems very slow during these tests.

@Arjen:

It appears the "nice" command does exist on Cygwin.  So I suggest you
try the above trick as well in your launch script to see if it helps
you to use your computer for other tasks during these tests.

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

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

Hi Alan,



> -----Original Message-----
> From: Alan W. Irwin [mailto:ir...@be...]
> Sent: Tuesday, December 13, 2016 9:28 PM
> @Arjen:
>
> Great.
>
> I should have emphasized you should drop all constraints for these comprehensive
> tests other than the ones that have proved absolutely necessary in the past for the
> given platform.
>
> So ideally your script launch (aside from the nice part, see below) should be
>
> scripts/comprehensive_test.sh --do_submit_dashboard yes --do_test_interactive no
>
> with very few if any further constraining options.
>
I noticed that when I ran the comprehensive tests for MinGW-w64/MSYS2 :). Attached is the complete output for that platform. I will run the Cygwin equivalent later today.

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

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

On 2016-12-14 07:52-0000 Arjen Markus wrote:

> Hi Alan,
>
>
>
>> -----Original Message-----
>> From: Alan W. Irwin [mailto:ir...@be...]
>> Sent: Tuesday, December 13, 2016 9:28 PM
>> @Arjen:
>>
>> Great.
>>
>> I should have emphasized you should drop all constraints for these comprehensive
>> tests other than the ones that have proved absolutely necessary in the past for the
>> given platform.
>>
>> So ideally your script launch (aside from the nice part, see below) should be
>>
>> scripts/comprehensive_test.sh --do_submit_dashboard yes --do_test_interactive no
>>
>> with very few if any further constraining options.
>>

> I noticed that when I ran the comprehensive tests for MinGW-w64/MSYS2 :). Attached is the complete output for that platform.

Thanks for that report.  The script completed without obvious issues
so this is what I will report at
<https://sourceforge.net/p/plplot/wiki/Testing_PLplot/#Testing%20Reports>
later today, and it is good enough for this release for this platform.  I think this is
your first comprehensive report for this platform
(at least I did not record anything at the above URL before) so
the large incompleteness you have in this report compared to what Greg
produced is understandable.  But I will follow up off list tomorrow
on the packages you should install post-release to create a much more
complete and powerful PLplot (comparable to or better than your Cygwin
version) to use and test on MinGW-w64/MSYS2 from now on.  Also, you
do need to update this platform before the next time you test it.  For example, I notice this
test was with CMake-3.4.3, and the latest version currently available for
this platform is 3.7.0 (which you should use from now on because the
minimum CMake version we now accept is 3.6.2 due to a commit I
made earlier today).

I will run the Cygwin equivalent later today.

Thanks in advance for that.  I imagine this is a very busy time for
you leading up to the Christmas holidays so I really appreciate the
comprehensive test results you have been producing for me early this
week. They are going to be a big help to me getting out this release
sooner (maybe even before Christmas) rather than later.

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

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

Hi Alan,



> -----Original Message-----
> From: Alan W. Irwin [mailto:ir...@be...]
> Sent: Wednesday, December 14, 2016 12:52 PM
>
> Thanks for that report.  The script completed without obvious issues so this is what
> I will report at
> <https://sourceforge.net/p/plplot/wiki/Testing_PLplot/#Testing%20Reports>
> later today, and it is good enough for this release for this platform.  I think this is
> your first comprehensive report for this platform (at least I did not record anything at
> the above URL before) so the large incompleteness you have in this report
> compared to what Greg produced is understandable.  But I will follow up off list
> tomorrow on the packages you should install post-release to create a much more
> complete and powerful PLplot (comparable to or better than your Cygwin
> version) to use and test on MinGW-w64/MSYS2 from now on.  Also, you do need
> to update this platform before the next time you test it.  For example, I notice this
> test was with CMake-3.4.3, and the latest version currently available for this
> platform is 3.7.0 (which you should use from now on because the minimum CMake
> version we now accept is 3.6.2 due to a commit I made earlier today).
>

I noticed that too - I have started the update procedure already. That leaves installing the additional packages.

> I will run the Cygwin equivalent later today.
>
> Thanks in advance for that.  I imagine this is a very busy time for you leading up to
> the Christmas holidays so I really appreciate the comprehensive test results you
> have been producing for me early this week. They are going to be a big help to me
> getting out this release sooner (maybe even before Christmas) rather than later.
>
It is indeed a busy time. I hope the Cygwin test finishes before I have to leave - for reasons best known or actually only known to itself, the clean step failed the first time I ran the tests, so I had to restart. (Could be interference from the virus scanner, I suppose.)

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

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

Hm,



Updating my MinGW-w64/MSYS2 installation was probably a bad idea:


$ ls
      1 [main] bash (13712) C:\msys64\usr\bin\bash.exe: *** fatal error - cygheap base mismatch detected - 0x180327400/0x1802FE408.
This problem is probably due to using incompatible versions of the cygwin DLL.
Search for cygwin1.dll using the Windows Start->Find/Search facility
and delete all but the most recent version.  The most recent version *should*
reside in x:\cygwin\bin, where 'x' is the drive on which you have
installed the cygwin distribution.  Rebooting is also suggested if you
are unable to find another cygwin DLL.
21123784 [main] bash 14692 fork: child -1 - forked process 13712 died unexpectedly, retry 0, exit code 0xC0000005, errno 11
bash: fork: retry: No child processes
      1 [main] bash (19412) C:\msys64\usr\bin\bash.exe: *** fatal error - cygheap base mismatch detected - 0x180327400/0x1802FE408.
This problem is probably due to using incompatible versions of the cygwin DLL.
Search for cygwin1.dll using the Windows Start->Find/Search facility
and delete all but the most recent version.  The most recent version *should*
reside in x:\cygwin\bin, where 'x' is the drive on which you have
installed the cygwin distribution.  Rebooting is also suggested if you
are unable to find another cygwin DLL.
22205898 [main] bash 14692 fork: child -1 - forked process 19412 died unexpectedly, retry 0, exit code 0xC0000005, errno 11
bash: fork: retry: No child processes

...



This is the result for any command I give now. The reference to Cygwin is also a trifle unexpected, though I know Cygwin is involved somewhere under the hood ...



I will have to reinstall it. Preferably at a quiet time, when no Cygwin shell is running :(.



Regards,



Arjen



I noticed that too - I have started the update procedure already. That leaves installing the additional packages.

>

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

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

On 2016-12-14 12:09-0000 Arjen Markus wrote:

> Hm,
>
> Updating my MinGW-w64/MSYS2 installation was probably a bad idea:
[...]
> I will have to reinstall it. Preferably at a quiet time, when no Cygwin shell is running :(.

Well, if I recall correctly, the last time we discussed the
MinGW-w64/MSYS2 version of cmake, the conclusion then was your install
of that platform had problems just like every other MinGW-w64/MSYS2
user at that time so a complete reinstall was recommended, but I
suspect you did not do that.  But now is your chance to do that in the
next several weeks.

Note there is no rush on that before Christmas since I think your
current test results are adequate for this release, but when you do
tackle MinGW-w64/MSYS2 testing again post-release starting with a
fresh install, I suggest you look very carefully at all the packages
at <http://repo.msys2.org/mingw/x86_64/> and
<http://repo.msys2.org/msys/x86_64/>. (From advice I got on the MSYS2
list these are the two fundamental x86_64 repositories you have access
to from a fresh install so they should always by definition be
completely up-to-date about what is possible for you to install on any
given day.)

Relying on my traditional MinGW/MSYS experience and for the "MSYS
Makefiles" generator you are using, I believe you should install the make
version from the "msys" repository.  And you should also install bash
from the "msys" repository because there is no other choice then that
on the mingw side.  However, for every package where there is a choice
(such as cmake, swig, the gcc-compiler suite, etc.,) you should
install packages from the "mingw" repository.  Does that installation
strategy make sense?

Note, Greg Jung found on this platform that CMake was linked with Qt5
so you had to stick with Qt5 for PLplot as well (or otherwise there
was a packaging conflict between Qt4 and Qt5).  But that is fine, if
Qt5 is already installed (due to your cmake installation), then the
PLplot build system will just find and use that with nothing
additional you have to do.

Likely the best advice I can give you for this Linux-like (except for
the core parts which are native Windows, of course) free software
distribution, is to keep careful file records of everything you
install and update.  (I have found that habit to be invaluable for
Debian.) Typically, I capture such output with the "tee" command, e.g.,

apt-get install python-pil |tee -a 20161202

where "apt-get install python-pil" is one Debian way to install the
python-pil package, and "tee -a 20161202" appends all the output from
that command to the file 20161202 (which keeps track of all
installation activity on that date for me) and also the tee command
echos its input to stdout (i.e., normally your terminal where you can
see it in case you have to respond interactively to an installation
question).

Also please look carefully at cmake.out warnings and get rid of those
as much as possible by installing absolutely everything required by
PLplot that is packaged by MinGW-w64/MSYS2.  Assuming you do that,
your next tests on this platform will be extremely powerful ones.  In
fact this could be the most powerful version of PLplot that you have
access to on Windows since MinGW-w64/MSYS2 packaging now appears to be
getting ahead of Cygwin packaging, e.g., MinGW-w64/MSYS2 already
packages CMake 3.7.0 (in the "mingw" repository) while Cygwin
packaging is still stuck with CMake-3.6.2.

BTW, I see the expected three good dashboards from your recent Cygwin
comprehensive test so I am looking forward to seeing the corresponding
report tarball which should finish your comprehensive testing for this
release with any luck at all.

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

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

Hi Alan,



> -----Original Message-----
> From: Alan W. Irwin [mailto:ir...@be...]
> Sent: Thursday, December 15, 2016 2:31 AM
>
> Well, if I recall correctly, the last time we discussed the
> MinGW-w64/MSYS2 version of cmake, the conclusion then was your install of that
> platform had problems just like every other MinGW-w64/MSYS2 user at that time
> so a complete reinstall was recommended, but I suspect you did not do that.  But
> now is your chance to do that in the next several weeks.
>
I will have to, the thing is completely unuseable ;).

>
> Likely the best advice I can give you for this Linux-like (except for the core parts
> which are native Windows, of course) free software distribution, is to keep careful
> file records of everything you install and update.  (I have found that habit to be
> invaluable for
> Debian.) Typically, I capture such output with the "tee" command, e.g.,
>
> apt-get install python-pil |tee -a 20161202
>
I usually redirect all output to a file and then examine that afterwards. Cygwin is easier in this respect: the setup program shows the installed packages itself.

>
> BTW, I see the expected three good dashboards from your recent Cygwin
> comprehensive test so I am looking forward to seeing the corresponding report
> tarball which should finish your comprehensive testing for this release with any luck
> at all.
>
See the attached tarball. It took a long time to run through all the tests and all the build configurations, but it finished without any complaints indeed.

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

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

On 2016-12-15 07:49-0000 Arjen Markus wrote:

> Hi Alan,
>
>
>
>> -----Original Message-----
>> From: Alan W. Irwin [mailto:ir...@be...]
>> Sent: Thursday, December 15, 2016 2:31 AM
>>
>> Well, if I recall correctly, the last time we discussed the
>> MinGW-w64/MSYS2 version of cmake, the conclusion then was your install of that
>> platform had problems just like every other MinGW-w64/MSYS2 user at that time
>> so a complete reinstall was recommended, but I suspect you did not do that.  But
>> now is your chance to do that in the next several weeks.
>>
> I will have to, the thing is completely unuseable ;).
>
>>
>> Likely the best advice I can give you for this Linux-like (except for the core parts
>> which are native Windows, of course) free software distribution, is to keep careful
>> file records of everything you install and update.  (I have found that habit to be
>> invaluable for
>> Debian.) Typically, I capture such output with the "tee" command, e.g.,
>>
>> apt-get install python-pil |tee -a 20161202
>>
> I usually redirect all output to a file and then examine that afterwards. Cygwin is easier in this respect: the setup program shows the installed packages itself.
>
>>
>> BTW, I see the expected three good dashboards from your recent Cygwin
>> comprehensive test so I am looking forward to seeing the corresponding report
>> tarball which should finish your comprehensive testing for this release with any luck
>> at all.
>>
> See the attached tarball. It took a long time to run through all the tests and all the build configurations, but it finished without any complaints indeed.

Hi Arjen:

That's a really nice piece of news to hear from you.  I will take a
look at the details in that report tomorrow and post it and your prior
report for MinGW-w64/MSYS2 on our wiki.

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

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

Hi Alan,



> -----Original Message-----
> From: Alan W. Irwin [mailto:ir...@be...]


> Hi Arjen:
>
> That's a really nice piece of news to hear from you.  I will take a look at the details
> in that report tomorrow and post it and your prior report for MinGW-w64/MSYS2 on
> our wiki.
>
Glad to hear that - my renewed installation of MinGW-w64/MSYS2 is misbehaving so I cannot produce any report for that platform at the 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] Comprehensive testing

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

Hi Alan,



It took some experimenting to get the installation of MinGW-w64/MSYS2 to work properly (some packages need to be installed via the full name - mingw-w64-x86_64-gcc for instance - to get the latest version and even then that does not always happen, for CMake for instance). But the comprehensive test succeeded for C, C++, Fortran, Tcl and Tk. Oddly enough, not for Python 2. Cmake seems unable to find the libraries or the header files. Well, I hope to have a look at that later.



Regards,



Arjen

From: Arjen Markus
Sent: Thursday, December 15, 2016 3:52 PM
To: 'Alan W. Irwin'
Cc: PLplot development list
Subject: RE: [Plplot-devel] Comprehensive testing


Hi Alan,



> -----Original Message-----
> From: Alan W. Irwin [mailto:ir...@be...]

> Hi Arjen:
>
> That's a really nice piece of news to hear from you.  I will take a look at the details
> in that report tomorrow and post it and your prior report for MinGW-w64/MSYS2 on
> our wiki.
>
Glad to hear that - my renewed installation of MinGW-w64/MSYS2 is misbehaving so I cannot produce any report for that platform at the 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] Comprehensive testing

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

On 2016-12-16 13:10-0000 Arjen Markus wrote:


> It took some experimenting to get the installation of
MinGW-w64/MSYS2 to work properly (some packages need to be installed
via the full name - mingw-w64-x86_64-gcc for instance - to get the
latest version and even then that does not always happen, for CMake
for instance). But the comprehensive test succeeded for C, C++,
Fortran, Tcl and Tk. Oddly enough, not for Python 2. Cmake seems
unable to find the libraries or the header files. Well, I hope to have
a look at that later.

Hi Arjen:

Thanks for this additional test on MinGW-w64/MSYS2 with your new
installation of that platform.

I have summarized this good test result (and also your prior good test
for Cygwin) at
<https://sourceforge.net/p/plplot/wiki/Testing_PLplot/#Testing%20Reports>

For your new installation of MinGW-w64/MSYS2 there is still a lot of
package installation incompleteness, see footnotes j1, C1, D1, D2, F1,
G2, H2, I1, and J1.  But it is a good start that is suitable for this
release, and I will remark more to you off list concerning how to
rectify that package incompleteness issue for the next time
(presumably post-release) when you repeat this comprehensive test.
(And for this test, if I got any of those footnotes wrong, please let me know, and
I will change them.)

I believe you mentioned previously that you planned to test the
combination of MSVC + ifort for this release?  If you have done that I
would appreciate you letting me know the results for our release notes
(concerning the part of those release notes detailing what new Fortran
binding tests were done.  Also, please let me know the version of MSVC
and ifort you used so I can record that in the release notes.

By the way, you might find as a result of those tests that you have to
upgrade bindings/f95/plplotf95_ifort.def since that was last updated
in February 2016 (!) and there have been some Fortran changes since.

Also, I have a feeling you have a Windows batch file you run to
automate your run-time testing of MSVC + ifort. Would you be willing
to distribute that file with PLplot [in the scripts subdirectory?] for
the benefit of other testers of the MSVC + ifort combination?

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

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

Hi Alan,

> -----Original Message-----
> From: Alan W. Irwin [mailto:ir...@be...]
> Sent: Saturday, December 17, 2016 4:00 AM
> To: Arjen Markus; PLplot development list
> Subject: RE: [Plplot-devel] Comprehensive testing
>
> Thanks for this additional test on MinGW-w64/MSYS2 with your new installation of
> that platform.
>
> I have summarized this good test result (and also your prior good test for Cygwin)
> at <https://sourceforge.net/p/plplot/wiki/Testing_PLplot/#Testing%20Reports>
>
> For your new installation of MinGW-w64/MSYS2 there is still a lot of package
> installation incompleteness, see footnotes j1, C1, D1, D2, F1, G2, H2, I1, and J1.
> But it is a good start that is suitable for this release, and I will remark more to you
> off list concerning how to rectify that package incompleteness issue for the next
> time (presumably post-release) when you repeat this comprehensive test.
> (And for this test, if I got any of those footnotes wrong, please let me know, and I
> will change them.)
>
I will have to look at this carefully ;). As well as your summarty of the MinGW-w64/MSYS2 package management in general. What I wrote was the result of empirical research. Your digging into the documentation should be quite valuable - the MinGW-w64/MSYS2 environment is useful, but confusing.

> I believe you mentioned previously that you planned to test the combination of
> MSVC + ifort for this release?  If you have done that I would appreciate you letting
> me know the results for our release notes (concerning the part of those release
> notes detailing what new Fortran binding tests were done.  Also, please let me
> know the version of MSVC and ifort you used so I can record that in the release
> notes.

I have not gotten around to that yet - ought to be simple enough, but currently I compare the files manually (there is a compare command under Windows, but it is downright useless - you cannot skip lines, nor will it compare lines, but only bytes). I have been thinking of a small script to the job, but I have not written it yet.

>
> By the way, you might find as a result of those tests that you have to upgrade
> bindings/f95/plplotf95_ifort.def since that was last updated in February 2016 (!) and
> there have been some Fortran changes since.
>
Hm, they have not popped up since then ...

> Also, I have a feeling you have a Windows batch file you run to automate your run-
> time testing of MSVC + ifort. Would you be willing to distribute that file with PLplot
> [in the scripts subdirectory?] for the benefit of other testers of the MSVC + ifort
> combination?
>
Yes, I can do that - it is very simple and straightforward, but it might be useful :).

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

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

On 2016-12-16 19:00-0800 Alan W. Irwin wrote:

> For your new installation of MinGW-w64/MSYS2 there is still a lot of
> package installation incompleteness, see footnotes j1, C1, D1, D2, F1,
> G2, H2, I1, and J1.  But it is a good start that is suitable for this
> release, and I will remark more to you off list concerning how to
> rectify that package incompleteness issue for the next time
> (presumably post-release) when you repeat this comprehensive test.
> (And for this test, if I got any of those footnotes wrong, please let me know, and
> I will change them.)
>
> I believe you mentioned previously that you planned to test the
> combination of MSVC + ifort for this release?  If you have done that I
> would appreciate you letting me know the results for our release notes
> (concerning the part of those release notes detailing what new Fortran
> binding tests were done.  Also, please let me know the version of MSVC
> and ifort you used so I can record that in the release notes.
>
> By the way, you might find as a result of those tests that you have to
> upgrade bindings/f95/plplotf95_ifort.def since that was last updated
> in February 2016 (!) and there have been some Fortran changes since.
>
> Also, I have a feeling you have a Windows batch file you run to
> automate your run-time testing of MSVC + ifort. Would you be willing
> to distribute that file with PLplot [in the scripts subdirectory?] for
> the benefit of other testers of the MSVC + ifort combination?

Hi Arjen:

Further to the above, I have now, at long last, updated the summary of
our comprehensive testing of the new Fortran binding at
<https://sourceforge.net/p/plplot/wiki/Testing_PLplot/#Fortran%20Testing%20Reports>.
The 5 new reports there are based on the Fortran subset of 4 recent
comprehensive test reports (Cygwin and MinGW-w64/MSYS2 from you, and
Debian Jessie with CMake-3.0.2 and CMake-3.7.0 from me) as well as a
special Ubuntu NAGFOR comprehensive test you did in July which showed
no warning or error messages at all from that high-quality,
standards-checking, Fortran compiler.  From the e-mail you wrote
back then, I have identified that platform as Ubuntu (I believe it
was on some virtual box you had available to you at work) with
NAGFOR compiler.  Can you retrieve any more details at this late
date about which version (i.e., codename) of Ubuntu, and which
numerical version of NAGFOR?  If so, please update that table item
in the wiki or send me that data so I can do that myself.

Also, the way I now have the general table of results set up at
<https://sourceforge.net/p/plplot/wiki/Testing_PLplot/#Testing%20Reports>
and the Fortran-specific table of results set up at
<https://sourceforge.net/p/plplot/wiki/Testing_PLplot/#Fortran%20Testing%20Reports>,
it should be straightforward to include your MSVC + ifort test results
in both with the addition of some footnotes.  So once you collect test
results for MSVC + ifort as above, please let me know which version of
MSVC and which version of ifort you used so I can put that information
in these summary tables. It would also be good to know which of our
standard examples were run for which languages by your hypothesized
batch file.  Also, if that hypothesized batch file actually exists
then please identify for the above tables which of our three different
build trees (core build tree, installed examples build tree, and
installed examples traditional build tree) it tests for each of our
three principal configurations (shared library + dynamic devices,
shared library + nondynamic devices, and static library + nondynamic
devices).  Also, if it is just one of those possibilities (e.g., some
examples were run in the build tree for default shared libraries +
dynamic devices), it is still well worth posting those limited testing
results in the above two tables.

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

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

Hi Alan,



> -----Original Message-----
> From: Alan W. Irwin [mailto:ir...@be...]
> The 5 new reports there are based on the Fortran subset of 4 recent
> comprehensive test reports (Cygwin and MinGW-w64/MSYS2 from you, and
> Debian Jessie with CMake-3.0.2 and CMake-3.7.0 from me) as well as a special
> Ubuntu NAGFOR comprehensive test you did in July which showed no warning or
> error messages at all from that high-quality, standards-checking, Fortran compiler.
> From the e-mail you wrote back then, I have identified that platform as Ubuntu (I
> believe it was on some virtual box you had available to you at work) with NAGFOR
> compiler.  Can you retrieve any more details at this late date about which version
> (i.e., codename) of Ubuntu, and which numerical version of NAGFOR?  If so,
> please update that table item in the wiki or send me that data so I can do that
> myself.
>
I have checked the Ubuntu version - not a codename but only: Ubuntu 16.04 LTS

NAG Fortran was version 6.1

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

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

On 2016-12-19 09:39-0000 Arjen Markus wrote:

> Hi Alan,
>
>
>
>> -----Original Message-----
>> From: Alan W. Irwin [mailto:ir...@be...]
>> The 5 new reports there are based on the Fortran subset of 4 recent
>> comprehensive test reports (Cygwin and MinGW-w64/MSYS2 from you, and
>> Debian Jessie with CMake-3.0.2 and CMake-3.7.0 from me) as well as a special
>> Ubuntu NAGFOR comprehensive test you did in July which showed no warning or
>> error messages at all from that high-quality, standards-checking, Fortran compiler.
>> From the e-mail you wrote back then, I have identified that platform as Ubuntu (I
>> believe it was on some virtual box you had available to you at work) with NAGFOR
>> compiler.  Can you retrieve any more details at this late date about which version
>> (i.e., codename) of Ubuntu, and which numerical version of NAGFOR?  If so,
>> please update that table item in the wiki or send me that data so I can do that
>> myself.
>>
> I have checked the Ubuntu version - not a codename but only: Ubuntu 16.04 LTS

> NAG Fortran was version 6.1

Hi Arjen:

Thanks very much for those two pieces of information.

>From <https://en.wikipedia.org/wiki/Ubuntu_version_history> 16.04 LTS
corresponds to codename "Xenial Xerus".  I will use both designations
in the report.

Wikipedia knows all.  :-)

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

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

On 2016-12-19 09:39-0000 Arjen Markus wrote:

>> -----Original Message-----
>> From: Alan W. Irwin [mailto:ir...@be...]
[...]
>> From the e-mail you wrote back then, I have identified that platform as Ubuntu (I
>> believe it was on some virtual box you had available to you at work) with NAGFOR
>> compiler.  Can you retrieve any more details at this late date about which version
>> (i.e., codename) of Ubuntu, and which numerical version of NAGFOR?  If so,
>> please update that table item in the wiki or send me that data so I can do that
>> myself.
>>
> I have checked the Ubuntu version - not a codename but only: Ubuntu 16.04 LTS
>
> NAG Fortran was version 6.1

Thanks for that info.  I have just now updated our wiki accordingly at
<https://sourceforge.net/p/plplot/wiki/Testing_PLplot/#Fortran%20Testing%20Reports>.

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

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

Hi Alan,



I just ran the little script I have for the examples in C, Fortran and Tcl. The PostScript files all came out identical for the corresponding examples. Here are the details for the two compilers:



Intel(R) Parallel Studio XE 2015

Copyright (C) 1985-2014 Intel Corporation. All rights reserved.

Intel(R) Parallel Studio XE 2015 Update 1 Composer Edition (package 148)





C:\Program Files (x86)\Intel\Composer XE 2015>cl -v

Microsoft (R) C/C++ Optimizing Compiler Version 18.00.40629 for x64

Copyright (C) Microsoft Corporation.  All rights reserved.




(See also remark below)

Regards,

Arjen


> -----Original Message-----
> From: Alan W. Irwin [mailto:ir...@be...]
> Sent: Sunday, December 18, 2016 12:52 AM
> >
> > I believe you mentioned previously that you planned to test the
> > combination of MSVC + ifort for this release?  If you have done that I
> > would appreciate you letting me know the results for our release notes
> > (concerning the part of those release notes detailing what new Fortran
> > binding tests were done.  Also, please let me know the version of MSVC
> > and ifort you used so I can record that in the release notes.
> >
> > By the way, you might find as a result of those tests that you have to
> > upgrade bindings/f95/plplotf95_ifort.def since that was last updated
> > in February 2016 (!) and there have been some Fortran changes since.
> >


PLplot built smoothlessly from a clean directory - so the Intel Fortran .def file is up to date.

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

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

On 2016-12-21 09:01-0000 Arjen Markus wrote:

> I just ran the little script I have for the examples in C, Fortran
and Tcl. The PostScript files all came out identical for the
corresponding examples. Here are the details for the two compilers:

Thanks for that critical test of the Microsoft C/C++ compiler + Intel compiler
and the further compiler details you supplied.

Could you also identify what cmake version you used, what generator
you used, and confirm your
tests were confined to the build tree with default shared libraries
and dynamic devices?

I have additional questions about terminology.  Is MSVC an IDE? (That
is implied by the wikipedia article about it.) Just out of curiosity
is the "Microsoft C/C++ optimizing compiler" the compiler used by that
IDE?  However, if I recall correctly, you use the command line and not
an IDE.  So does that mean you are using nmake on the command line? I
believe I have often described your tests as MSVC +ifort, but it
appears that is not correct, if MSVC is an IDE that you are not
actually using.

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

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

Hi Alan,



See below

> -----Original Message-----
> From: Alan W. Irwin [mailto:ir...@be...]
> Sent: Wednesday, December 21, 2016 11:50 AM
> To: Arjen Markus
> Cc: PLplot development list
> Subject: RE: [Plplot-devel] Comprehensive testing
>
> On 2016-12-21 09:01-0000 Arjen Markus wrote:
>
> > I just ran the little script I have for the examples in C, Fortran
> and Tcl. The PostScript files all came out identical for the corresponding examples.
> Here are the details for the two compilers:
>
> Thanks for that critical test of the Microsoft C/C++ compiler + Intel compiler and the
> further compiler details you supplied.
>
> Could you also identify what cmake version you used, what generator you used,
> and confirm your tests were confined to the build tree with default shared libraries
> and dynamic devices?
>
CMake 3.4.3, with the "NMake Makefiles" generator. The complete command line for this was:

d:\cmake3.4.3\bin\cmake ..\plplot-git -G "NMake Makefiles" -DBUILD_TEST=ON -DENABLE_java=OFF -DPLD_wxwidgets=OFF

> I have additional questions about terminology.  Is MSVC an IDE? (That is implied
> by the wikipedia article about it.) Just out of curiosity is the "Microsoft C/C++
> optimizing compiler" the compiler used by that IDE?  However, if I recall correctly,
> you use the command line and not an IDE.  So does that mean you are using
> nmake on the command line? I believe I have often described your tests as MSVC
> +ifort, but it appears that is not correct, if MSVC is an IDE that you are not actually
> using.
>
Well, MSVC (MicroSoft Visual C++) is the compiler and it is usual to use it in combination with the MicroSoft Visual Studio IDE, but it is perfectly possible to use it from the command-line. And that is what I do in the case of PLplot. One reason is that it is easier to automate things (if you use the Visual Studio generator - and you have carefully selected the right version - you get a complex or at least extensive set of projects, each to build a single component of PLplot). Another is that I like working from the command-line. It gives me more control :).

So, the concise description is correct.

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

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

On 2016-12-21 11:04-0000 Arjen Markus wrote:

>> -----Original Message-----
>> From: Alan W. Irwin [mailto:ir...@be...]
[...]
>> I have additional questions about terminology.  Is MSVC an IDE? (That is implied
>> by the wikipedia article about it.) Just out of curiosity is the "Microsoft C/C++
>> optimizing compiler" the compiler used by that IDE?  However, if I recall correctly,
>> you use the command line and not an IDE.  So does that mean you are using
>> nmake on the command line? I believe I have often described your tests as MSVC
>> +ifort, but it appears that is not correct, if MSVC is an IDE that you are not actually
>> using.
>>
> Well, MSVC (MicroSoft Visual C++) is the compiler and it is usual to use it in combination with the MicroSoft Visual Studio IDE, but it is perfectly possible to use it from the command-line. And that is what I do in the case of PLplot. One reason is that it is easier to automate things (if you use the Visual Studio generator - and you have carefully selected the right version - you get a complex or at least extensive set of projects, each to build a single component of PLplot). Another is that I like working from the command-line. It gives me more control :).
>
> So, the concise description is correct.

Hi Arjen:

Thanks for the additional information you gave about your test
conditions and also your clarifying explanation above that MSVC is not an IDE but
often used in conjunction with one.  Which is not consistent with what
the wikipedia article <https://en.wikipedia.org/wiki/Visual_C++> says
(for example, in their summary box they say MSVC is an IDE), but I
suspect they got it wrong this time.

One naming convention still has me confused.  You reported

> C:\Program Files (x86)\Intel\Composer XE 2015>cl -v

> Microsoft (R) C/C++ Optimizing Compiler Version 18.00.40629 for x64

There is no mention there of "Visual" so is this some different
compiler than MSVC?

My working hypothesis to explain this difference in nomenclature is
MSVC is actually a suite of products including this compiler, a
debugger, and a lot of machinery (which you don't use) to make it all
work with the Visual Studio IDE.  But I would appreciate your
confirmation of that hypothesis.

If that hypothesis is correct, it might be better to use the shorthand
(and more recognizable) description MSVC to describe your compiler as
opposed to "C/C++ Optimizing Compiler Version 18.00.40629", but I
would need to know your MSVC version number in that case.

Actually, what I need here is your advice on the best way to designate
your C/C++ and Intel Fortran compiler versions in a way that Windows
developers will instantly recognize, and I will follow that advice.

By the way, it is even more confusing in the free compiler world;
"gcc" is the name of the suite of compilers for C, C++, Fortran, etc.,
but "gcc" is also the name for the C compiler subset of that suite.
:-)

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

[<p.d...@gm...>]

I must confess that I use msvc and visual studio them interchangeably. But can't visual studio do visual basic and c# too? I sort of assumed msvc was the c/c++ bit of visual studio. But I'd be happy to learn different.

I always though the visual bit referred to fact that you could draw windows and visual studio would generate code for you. But I only ever tried this once (in visual studio 6 I think) and don't know if that feature still exists.

Phil

Sent from my Windows 10 phone

From: Alan W. Irwin
Sent: 21 December 2016 19:25
To: Arjen Markus
Cc: PLplot development list
Subject: Re: [Plplot-devel] Comprehensive testing

On 2016-12-21 11:04-0000 Arjen Markus wrote:

>> -----Original Message-----
>> From: Alan W. Irwin [mailto:ir...@be...]
[...]
>> I have additional questions about terminology.  Is MSVC an IDE? (That is implied
>> by the wikipedia article about it.) Just out of curiosity is the "Microsoft C/C++
>> optimizing compiler" the compiler used by that IDE?  However, if I recall correctly,
>> you use the command line and not an IDE.  So does that mean you are using
>> nmake on the command line? I believe I have often described your tests as MSVC
>> +ifort, but it appears that is not correct, if MSVC is an IDE that you are not actually
>> using.
>>
> Well, MSVC (MicroSoft Visual C++) is the compiler and it is usual to use it in combination with the MicroSoft Visual Studio IDE, but it is perfectly possible to use it from the command-line. And that is what I do in the case of PLplot. One reason is that it is easier to automate things (if you use the Visual Studio generator - and you have carefully selected the right version - you get a complex or at least extensive set of projects, each to build a single component of PLplot). Another is that I like working from the command-line. It gives me more control :).
>
> So, the concise description is correct.

Hi Arjen:

Thanks for the additional information you gave about your test
conditions and also your clarifying explanation above that MSVC is not an IDE but
often used in conjunction with one.  Which is not consistent with what
the wikipedia article <https://en.wikipedia.org/wiki/Visual_C++> says
(for example, in their summary box they say MSVC is an IDE), but I
suspect they got it wrong this time.

One naming convention still has me confused.  You reported

> C:\Program Files (x86)\Intel\Composer XE 2015>cl -v

> Microsoft (R) C/C++ Optimizing Compiler Version 18.00.40629 for x64

There is no mention there of "Visual" so is this some different
compiler than MSVC?

My working hypothesis to explain this difference in nomenclature is
MSVC is actually a suite of products including this compiler, a
debugger, and a lot of machinery (which you don't use) to make it all
work with the Visual Studio IDE.  But I would appreciate your
confirmation of that hypothesis.

If that hypothesis is correct, it might be better to use the shorthand
(and more recognizable) description MSVC to describe your compiler as
opposed to "C/C++ Optimizing Compiler Version 18.00.40629", but I
would need to know your MSVC version number in that case.

Actually, what I need here is your advice on the best way to designate
your C/C++ and Intel Fortran compiler versions in a way that Windows
developers will instantly recognize, and I will follow that advice.

By the way, it is even more confusing in the free compiler world;
"gcc" is the name of the suite of compilers for C, C++, Fortran, etc.,
but "gcc" is also the name for the C compiler subset of that suite.
:-)

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
__________________________

------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/intel
_______________________________________________
Plplot-devel mailing list
Plp...@li...
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Re: [Plplot-devel] Comprehensive testing

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

Hi Arjen:

I have just described your recent MSVC + ifort platform tests as the
first item in the two tables at 
<https://sourceforge.net/p/plplot/wiki/Testing_PLplot/#Testing%20Reports>
and
<https://sourceforge.net/p/plplot/wiki/Testing_PLplot/#Fortran%20Testing%20Reports>.
Please take a careful look at the footnote (called "l" in that former
table and "d" in that latter table, but the wording is identical for
those two different footnotes).  I believe I have come up with a
resonable designation for your MSVC compiler in those footnotes, but
feel free to advise me if you think I can improve on that.  Also, note
the two ??? values that are in that footnote now corresponding to the
Tcl version you use and general site where you obtained that version
of Tcl.  Could you please let me know that information so I can
replace those ??? values or else update those two separate footnotes
yourself?

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

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

Hi Alan,

> -----Original Message-----
> From: Alan W. Irwin [mailto:ir...@be...]
> Sent: Thursday, December 22, 2016 1:15 AM
> To: Arjen Markus
> Cc: PLplot development list
> Subject: Re: [Plplot-devel] Comprehensive testing
>
> Hi Arjen:
>
> I have just described your recent MSVC + ifort platform tests as the first item in the
> two tables at
> <https://sourceforge.net/p/plplot/wiki/Testing_PLplot/#Testing%20Reports>
> and
> <https://sourceforge.net/p/plplot/wiki/Testing_PLplot/#Fortran%20Testing%20Repor
> ts>.
> Please take a careful look at the footnote (called "l" in that former table and "d" in
> that latter table, but the wording is identical for those two different footnotes).  I
> believe I have come up with a resonable designation for your MSVC compiler in
> those footnotes, but feel free to advise me if you think I can improve on that.  Also,
> note the two ??? values that are in that footnote now corresponding to the Tcl
> version you use and general site where you obtained that version of Tcl.  Could you
> please let me know that information so I can replace those ??? values or else
> update those two separate footnotes yourself?
>
I have just added the version and origin information for Tcl in the Wiki page.

As for the designation of the C/C++ and Fortran compilers: as far as I am aware "everybody" uses the terms now in that Wiki page. The official designations you get with the options to report the version are confusing in my opinion - what is a composer other than someone writing a piece of music? (Those terms seem to originate with the marketing department of the various companies.)

The short message therefore is that with the concise and the detailed designations the software has been uniquely identified.

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

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

On 2016-12-22 08:27-0000 Arjen Markus wrote:

> I have just added the version and origin information for Tcl in the Wiki page.

Thanks, Arjen.  I tweaked that footnote a bit more than propagated all
changes to the (duplicate) footnote for the other table.  While doing
that, it struck me that although the current description of your batch
file (taken from your e-mail) does not include C++, those examples are
built in any case by nmake. So the next time you use that batch file
you may want to add the C++ examples as well.

Also, would you be willing to copy your batch file to the scripts
directory and commit it?  It sounds like it would be useful to other
MSVC + ifort testers.

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

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

Hi Alan,



> -----Original Message-----
> From: Alan W. Irwin [mailto:ir...@be...]
> Sent: Thursday, December 22, 2016 10:25 AM
> To: Arjen Markus
> Cc: PLplot development list
> Subject: RE: [Plplot-devel] Comprehensive testing
>
> On 2016-12-22 08:27-0000 Arjen Markus wrote:
>
> > I have just added the version and origin information for Tcl in the Wiki page.
>
> Thanks, Arjen.  I tweaked that footnote a bit more than propagated all changes to
> the (duplicate) footnote for the other table.  While doing that, it struck me that
> although the current description of your batch file (taken from your e-mail) does not
> include C++, those examples are built in any case by nmake. So the next time you
> use that batch file you may want to add the C++ examples as well.
>
> Also, would you be willing to copy your batch file to the scripts directory and commit
> it?  It sounds like it would be useful to other MSVC + ifort testers.
>
Yes, that is an omission in the script. I now use a Tcl script to compare the files (because of lack of a suitable command under Windows - sigh) but a small C program to do the same may be more appropriate - we can be sure there is a C compiler on the machine, but not anything else. Also my current script simply takes for granted that the various languages are supported. I should make it a trifle more robust before releasing it to the outside world :). I will take care of both issues, not sure when, as the coming festivities will exact their toll on my time.

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.