Re: error using control package on openSuse 11.4

[Lukas Reichlin]

On 02.12.2011, at 12:06, Huub van Niekerk wrote:

> On Fri, Dec 2, 2011 at 11:16 AM, Lukas Reichlin <address@hidden> wrote:
> On 02.12.2011, at 10:45, Huub van Niekerk wrote:
> 
>> Hi,
>> 
>> Using octave 3.4.2 I'm trying to use control v. 2.2.0 which I installed 
>> using the packagemanager. However, when I typ "ver" in octave, it says 
>> ----------------------------------------------------------------------
>> GNU Octave Version 3.4.2
>> GNU Octave License: GNU General Public License
>> Operating System: Linux 2.6.37.6-0.9-default #1 SMP 2011-10-19 22:33:27 
>> +0200 i686
>> ----------------------------------------------------------------------
>> no packages installed.
>> 
>> Also, querying which octave packages are installed gives:
>> 
>> octave-forge-20111010-6.18.noarch
>> octave-forge-control-2.2.0-6.18.noarch
>> octave-devel-3.4.2-1.1.i586
>> octave-forge-nnet-0.1.13-6.18.noarch
>> octave-3.4.2-1.1.i586
>> octave-forge-linear-algebra-2.0.0-6.18.noarch
>> 
>> What's going wrong here?
>> 
>> Thank you.
>> _______________________________________________
>> Help-octave mailing list
>> address@hidden
>> https://mailman.cae.wisc.edu/listinfo/help-octave
> 
> To me it looks if Suse's package manager doesn't register the packages with 
> octave. First, try if this command is working:
> 
> sys = ss (-1, 1, 1, 0)
> 
> If it works, the problem is of cosmetic nature.
> If it doesn't work, the problem is serious and you should report it to Suse.
> 
> As a workaround, you can install the control package by octave's own package 
> manager. To do so, type inside octave:
> 
> pkg install -forge control
> 
> It may take several minutes to complete and you may see some verbose 
> warnings. Afterwards, you can check if it works by sys = ss (-1, 1, 1, 0) 
> again.
> 
> Lukas
> 
> Hi,
> 
> Thank you for your answers. Unfortunately, neither the first option nor the 
> work-around works. So I'll report it to Suse. Also, I got this:
> 
> pkg install -forge control
> AB08ND.f: In function ‘ab08nd’:
> AB08ND.f:265:0: warning: ‘wrkopt’ may be used uninitialized in this function
> MB03OY.f: In function ‘mb03oy’:
> MB03OY.f:198:0: warning: ‘aii’ may be used uninitialized in this function
> MB03PY.f: In function ‘mb03py’:
> MB03PY.f:201:0: warning: ‘aii’ may be used uninitialized in this function
> In file included from /usr/include/octave-3.4.2/octave/../octave/ov.h:43:0,
>                 from /usr/include/octave-3.4.2/octave/../octave/oct-obj.h:34,
>                 from /usr/include/octave-3.4.2/octave/../octave/ov-fcn.h:32,
>                 from 
> /usr/include/octave-3.4.2/octave/../octave/ov-builtin.h:28,
>                 from 
> /usr/include/octave-3.4.2/octave/../octave/defun-int.h:28,
>                 from 
> /usr/include/octave-3.4.2/octave/../octave/defun-dld.h:30,
>                 from /usr/include/octave-3.4.2/octave/../octave/oct.h:36,
>                 from slab08nd.cc:30:
> /usr/include/octave-3.4.2/octave/../octave/oct-hdf5.h:27:18: fatal error: 
> hdf5.h: No such file or directory
> compilation terminated.
> make: *** [slab08nd.oct] Error 1
> 'make' returned the following error: make: Entering directory 
> `/tmp/oct-VLkHnT/control/src'
> mkoctfile slab08nd.cc \
>              AB08ND.f AB08NX.f TB01ID.f MB03OY.f MB03PY.f
> make: Leaving directory `/tmp/oct-VLkHnT/control/src'
> error: called from `pkg>configure_make' in file 
> /usr/share/octave/3.4.2/m/pkg/pkg.m near line 1339, column 9
> error: called from:
> error:   /usr/share/octave/3.4.2/m/pkg/pkg.m at line 790, column 5
> error:   /usr/share/octave/3.4.2/m/pkg/pkg.m at line 361, column 9
>> 
> 
> It there a package conflict?

I guess that Suse's octave package is somehow (partially) broken. For example, 
hdf5 is not found/not deactived. Unfortunately, there's little I can do here, 
the problem must be fixed by Suse. If needed, Suse maintainers may ask the guys 
from Fedora for some tips because Fedora 16 has working packages of recent 
octave and control versions.

Lukas