Re: [Plplot-devel] I would appreciate some help tracking down the cause of a -DPLPLOT_USE_QT5=ON segfault

2015-03-12 Thread Alan W. Irwin
On 2015-03-12 08:05- Andrew Ross wrote: On Wed, Mar 11, 2015 at 05:38:47PM -0700, Alan Irwin wrote: On 2015-03-11 22:32- Andrew Ross wrote: On Wed, Mar 11, 2015 at 02:55:16PM -0700, Alan Irwin wrote: On 2015-03-11 21:29- Andrew Ross wrote: A minimal C / C++ / qt5 build of

Re: [Plplot-devel] Release status

2015-03-12 Thread Jim Dishaw
On Mar 12, 2015, at 7:06 AM, Phil Rosenberg p.d.rosenb...@gmail.com wrote: This thread is becoming a bit unwieldy, but I will try to answer below @Jim I had already written and tested a fix for the hatchings and have just committed it, sorry if you spent time on this. No problem. It was

Re: [Plplot-devel] Static build

2015-03-12 Thread Alan W. Irwin
On 2015-03-12 19:59-0400 Jim Dishaw wrote: What is the option for a pure static build on linux. I tried BUILD_SHARED_LIBS=OFF and it still linked to some dynamic libraries like Qt. Hi Jim: This is an interesting question. Static linking is a difficult thing to get right so the last answer at

Re: [Plplot-devel] Release status

2015-03-12 Thread Jim Dishaw
On Mar 12, 2015, at 2:13 PM, Alan W. Irwin ir...@beluga.phys.uvic.ca wrote: On 2015-03-11 14:49-0700 Alan W. Irwin wrote: Hi Phil: I just saw your one-line fix at http://sourceforge.net/p/plplot/plplot/ci/4e93f99a84a5c72d253c8791f813400ba2f46ff6. Does that really do the job? For

[Plplot-devel] Release status: exposing plhrsh

2015-03-12 Thread Alan W. Irwin
On 2015-03-12 11:13-0700 Alan W. Irwin wrote: @Phil, Jim: The recent exposure of plhrsh is not complete and has visibility issues for the shared library case. In all cases where a private function like this needs to be exposed, you need a declaration in include/plplotP.h using the

[Plplot-devel] Release status: plmeta/plrender

2015-03-12 Thread Alan W. Irwin
Hi Jim: Here are the results of a simple test I tried with -DPLD_plmeta=ON # Build what is relevant make plrender make plmeta make x01c make ps # Test examples/c/x01c -dev psc -o test1.psc examples/c/x01c -dev plmeta -o test.plmeta utils/plrender test.plmeta -dev psc -o test2.psc There were no

[Plplot-devel] Release status: plmetafile.c and plbuf.c compiler warnings

2015-03-12 Thread Alan W. Irwin
To Phil: gcc is generating these warnings when building libplplot. Would you please take a look to see whether this is either a real uninitialized issue that needs to be fixed or a false alarm? /home/software/plplot/HEAD/plplot.git/src/plmetafile.c: In function ‘read_header’:

Re: [Plplot-devel] Release status

2015-03-12 Thread Alan W. Irwin
On 2015-03-11 14:49-0700 Alan W. Irwin wrote: Hi Phil: I just saw your one-line fix at http://sourceforge.net/p/plplot/plplot/ci/4e93f99a84a5c72d253c8791f813400ba2f46ff6. Does that really do the job? For example, I noticed earlier in that code a test of pls-device rather than pls-dev, but

[Plplot-devel] Static build

2015-03-12 Thread Jim Dishaw
What is the option for a pure static build on linux. I tried BUILD_SHARED_LIBS=OFF and it still linked to some dynamic libraries like Qt. -- Dive into the World of Parallel Programming The Go Parallel Website,

Re: [Plplot-devel] Release status: plmeta/plrender

2015-03-12 Thread Alan W. Irwin
Hi Jim: Could you clarify the purpose of the -mfi and -mfo options and the plreadmetafile routine? It appears the options simply set metafile input and output file names without doing anything else contrary to their self documentation in src/plargs.c of Read the specified PLplot metafile and

Re: [Plplot-devel] Release status

2015-03-12 Thread Phil Rosenberg
This thread is becoming a bit unwieldy, but I will try to answer below @Jim I had already written and tested a fix for the hatchings and have just committed it, sorry if you spent time on this. Regarding the plhrsh issue, my build is fine - although it is a static build, so perhaps that is the

Re: [Plplot-devel] Release status: plmeta/plrender

2015-03-12 Thread Jim Dishaw
On Mar 12, 2015, at 6:08 PM, Alan W. Irwin ir...@beluga.phys.uvic.ca wrote: Hi Jim: Could you clarify the purpose of the -mfi and -mfo options and the plreadmetafile routine? -mfi sets the file name that plreadmetafile will use if one is not otherwise specified by the caller. Nothing