Re: [Plplot-devel] Poor RC1 test results on Debian woody

[Joao C. <jc...@fe...>]

On Tuesday 15 April 2003 22:03, Alan W. Irwin wrote:
...

|  *** There was one nasty RC1 failure for the combination of octave and png
|  device.
|
|  Opened p16.png.01
|
|  *** PLPLOT WARNING ***
|  plsfam: Must be called before plinit.
|
|  *** PLPLOT WARNING ***
|  plsdev: Must be called before plinit.
|  Plplot library version: 5.2.1.rc1
|
|  followed by a whole bunch of garbage output.

The problem you report happened  with me once. I couldn't reproduce it 
afterwards.

If you do:

octave:1> figure(1,"png","po.png");
Opened po.png
octave:2> p16
octave:3> closefig

everything is OK. That is exactly what test_octave.sh does.
Thus the problem must be somewhere else, either in test_octave.sh or 
plplot-test.sh, but I can't find where (and the other examples work fine).

The above test was done with octave-2.1.36, running octave in bindings/octave, 
and as a regular user, with the installed plplot, setting first

LOADPATH="/usr/local/test/share/plplot_octave//:/usr/local/test/lib/plplot5.2.1.rc1/examples/octave//:"

|  Warnings.
|
|  I did notice some warnings along the way.  configure still outputs the
|  following:
|
|  configure: WARNING: itclDecls.h: present but cannot be compiled
|  configure: WARNING: itclDecls.h: check for missing prerequisite headers?
|  configure: WARNING: itclDecls.h: proceeding with the preprocessor's result
|  configure: WARNING:     ## ------------------------------------ ##
|  configure: WARNING:     ## Report this to bug...@gn.... ##
|  configure: WARNING:     ## ------------------------------------ ##

Interestingly this WARNING does not occurs with RH-8.0. But occurs with 
suse-8.1. Since I can remember.

|  * /usr/bin/g++ -c -fPIC -I/usr/include/octave-2.1.35
|  -I/usr/include/octave-2.1.35/
|  octave -I/usr/include -mieee-fp -fno-implicit-templates -O2 -I.
|  plplot_octave.cc
|   -o plplot_octave.o
|   In file included from /usr/include/octave-2.1.35/octave/oct.h:31,
|                    from plplot_octave.cc:11:
|  		  /usr/include/octave-2.1.35/octave/config.h:148: warning:
|  HAVE_ISINF' redefined
|  ../../config.h:36: warning: this is the location of the previous
| definition /usr/include/octave-2.1.35/octave/config.h:151: warning:
| HAVE_ISNAN' redefined ../../config.h:39: warning: this is the location of
| the previous definition /usr/include/octave-2.1.35/octave/config.h:288:
| warning: HAVE_FINITE' redefined
|  ../../config.h:24: warning: this is the location of the previous
| definition /usr/include/octave-2.1.35/octave/config.h:474: warning:
| HAVE_USLEEP' redefined
|  ../../config.h:101: warning: this is the location of the previous
| definition

I had already reported this one, and said that it was unavoidable and 
harmless. Octave configure.h, that is used when compiling any user octave 
function, also defines HAVE_ISINF etc, and thus the clash.

Joao