Re: gf undefined - ( my error ? )

[Mike Miller]

On Mon, Jul 29, 2013 at 10:02:08 -0700, seapwc wrote:
> octave:1> pkg load communications
> octave:2> paths=strsplit(path,":")
> paths =
> {
>   [1,1] = .
>   [1,2] = /usr/share/octave/packages/communications-1.1.0
>   [1,3] = /usr/share/octave/packages/image-1.0.15
>   [1,4] = /usr/share/octave/packages/signal-1.1.2
>   [1,5] = 
> /usr/lib/octave/packages/control-2.4.0/i686-redhat-linux-gnu-api-v48+
>   [1,6] = /usr/share/octave/packages/control-2.4.0
>   [1,7] = /usr/share/octave/packages/specfun-1.1.0
>   [1,8] = /usr/share/octave/packages/optim-1.0.17
>   [1,9] = /usr/share/octave/packages/struct-1.0.9
>   [1,10] = /usr/share/octave/packages/miscellaneous-1.0.11
>   [1,11] = /usr/share/octave/packages/audio-1.1.4
> [...]

So you can see in this list which packages were loaded, and for some
reason Octave is not adding the architecture-dependent paths for
several packages, including signal, image, and communications. They
should all have a "i686-redhat-linux-gnu-api-v48+" path component
each. I assume that's the right architecture string for your host
because it *is* being found for the control package. The following
will show what the right string is for your system:

  octave:1> octave_config_info ("canonical_host_type")
  ans = i686-pc-linux-gnu
  octave:2> octave_config_info ("api_version")
  ans = api-v48+

I am not running Fedora, you might want to confirm what you're seeing
with another Fedora user or try installing fresh on another system. If
it's not just your system, there may be a bug in the Fedora packaging
of some of these Forge packages.

HTH,

-- 
mike