Re: octave 3.7.7 doesn't find gnuplot

[Werner Koenig]

On 01.10.2013 06:44, Andreas Weber wrote:
> Am 30.09.2013 22:15, schrieb Werner Koenig:
> > recently I have installed a new octave 3.7.7 on my openSuse 12.3. Now on
> > the first try outs this octave doesn't find my installed gnuplot.
> >
> > A simple command plot(1:10) and you get the following error.
> > error: popen2: popen2 (child): unable to start process -- Datei oder
> > Verzeichnis nicht gefunden
> > error: called from:
> > error:
> > /opt/octave/share/octave/3.7.7+/m/plot/private/__gnuplot_open_stream__.m
> > at line 30, column 40
> > error: /opt/octave/share/octave/3.7.7+/m/plot/__gnuplot_drawnow__.m at
> > line 72, column 19
> > sh: : command not found
> > error: 'unset' undefined near line 1 column 1
> > warning: broken pipe
> Hallo Werner,
>
> See __gnuplot_open_stream__.m:30
> What does "[prog, args] = gnuplot_binary ()" give you in octave?
>
> What about "which gnuplot" in a terminal?
>
> ./configure found gnuplot? See for example my config.log:
>
> ~/src/octave-build$ grep -C1 gnuplot config.log
> configure:8332: result: gs
> configure:8371: checking for gnuplot
> configure:8387: found /usr/bin/gnuplot
> configure:8398: result: gnuplot
> configure:8444: checking for less
> --
>    Default pager:               less
>    gnuplot:                     gnuplot
>
> --
> ac_cv_prog_GHOSTSCRIPT=gs
> ac_cv_prog_GNUPLOT=gnuplot
> ac_cv_prog_GPERF=gperf
> --
> GNULIB__EXIT='0'
> GNUPLOT='gnuplot'
> GPERF='gperf
>
> Gruß, Andy
Hallo Andy,

thanks for the quick help. I think, I have to read the config.log 
carefully. Here I find

configure:8383: checking for gnuplot
configure:8413: result: no

Now the reason seams to be clear. Some weeks ago I crashed my openSuse 
Version 12.2
So I have installed a new openSuse 12.3, but not with all packages. On 
config time of
octave 3.7.7 obviously, there was no gnuplot installed. An installation 
of gnuplot without
reconfiguring octave 3.7.7 made available gnuplot for my system, but it 
don't correct
the error in octave 3.7.7. So I have to reconfigure and make a new build 
for octave 3.7.7,
than I think the error is gone. I will try it tonight.

So long Werner