Re: [Plplot-devel] Continuous Integration

2016-11-23 Thread Alan W. Irwin
@Andrew: I have CC'd you because you are the maintainer for the liblasi-dev Debian (and indirectly Ubuntu) package, and this e-mail provides some background (scan below to the error involving freetype) for a bug report I just made for that package at

Re: [Plplot-devel] Continuous Integration

2016-11-23 Thread Hazen Babcock
On 11/23/2016 06:08 AM, Alan W. Irwin wrote: > > Sorry for the length of this, but I have a lot to say that should be a > big help to you for testing purposes. No problem, I appreciate your thoughts and help. > * -- WARNING: CMAKE_VERSION = 3.2.2 is in the range from 3.2 through > 3.3.1 which h

Re: [Plplot-devel] Continuous Integration

2016-11-23 Thread Arjen Markus
Hi Alan, > -Original Message- > From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca] > > Hi Arjen: > > Just to interject, you have been tempted before to go down this road of > attempting > to support gfortran-4.8. But I have always argued against that for the > following > reasons:

Re: [Plplot-devel] Continuous Integration

2016-11-23 Thread Alan W. Irwin
On 2016-11-23 12:40- Arjen Markus wrote: > Hi Hazen, > > > > I see ... this is really a problem of the older version of gfortran. I tried > the code below with version 5.4, just to make sure: > > > > module passing_c > >use iso_c_binding > > > >implicit none > > contains > > subroutin

Re: [Plplot-devel] Continuous Integration

2016-11-23 Thread Arjen Markus
problem. Regards, Arjen > -Original Message- > From: Hazen Babcock [mailto:hbabc...@mac.com] > Sent: Wednesday, November 23, 2016 1:11 PM > To: Arjen Markus > Cc: PLplot development list > Subject: Re: [Plplot-devel] Continuous Integration > > > > On 11/

Re: [Plplot-devel] Continuous Integration

2016-11-23 Thread Hazen Babcock
On 11/23/2016 02:52 AM, Arjen Markus wrote: > > Nevertheless, do you have an error report for gfortran 4.8? We have seen > a few issues when we started on this, but I do not remember whether they > were serious and with the newer version they have disappeared. (The NAG > compiler is rather picky

Re: [Plplot-devel] Continuous Integration

2016-11-23 Thread Alan W. Irwin
On 2016-11-22 23:07-0500 Hazen Babcock wrote: > > On 11/20/2016 01:12 PM, Tom Schoonjans wrote: >> That’s exactly how I do it though: trial and error :-) > > I think I have at least sort of figured out travis-vi. To make it easier > I've been doing all the experiments on a personal copy of the PLp

Re: [Plplot-devel] Continuous Integration

2016-11-22 Thread Arjen Markus
not following the standard ;)). Regards, Arjen > -Original Message- > From: Hazen Babcock [mailto:hbabc...@mac.com] > Sent: Wednesday, November 23, 2016 5:07 AM > To: Tom Schoonjans > Cc: PLplot development list > Subject: Re: [Plplot-devel] Continuous Integration &

Re: [Plplot-devel] Continuous Integration

2016-11-22 Thread Hazen Babcock
On 11/20/2016 01:12 PM, Tom Schoonjans wrote: > That’s exactly how I do it though: trial and error :-) I think I have at least sort of figured out travis-vi. To make it easier I've been doing all the experiments on a personal copy of the PLplot repo. It is pretty cool to be able to build 5 diff

Re: [Plplot-devel] Continuous Integration

2016-11-20 Thread Tom Schoonjans
Hi Hazen, That’s exactly how I do it though: trial and error :-) If you worry about the commit history, then I recommend you do this in a separate branch, open a PR, commit until you get it right and then use “squash and merge”. In fact I recommend you make master a protected branch meaning tha

[Plplot-devel] Continuous Integration

2016-11-20 Thread Hazen Babcock
Hi Tom, Any pointers for getting started with continuous integration? I'm planning to set this up on the Github PLplot mirror using Travis-CI to start. In particular I'd like to know what you think is the best way to go about debugging the Travis scripts? It appears to me that this is going