[Octave-bug-tracker] [bug #48601] 4.0.3 has build packages mismatch with 4.0.1

[Hartmut]

Follow-up Comment #6, bug #48601 (project octave):

Running the tests of the signal package (as in comment #3) with the full path
string (no tilde any more) I get "PASS   454, FAIL  48, XFAIL  1". And
according to the generated fntest.log the failing tests are due to not finding
the oct-file of the signal package. 
Examples:

>>>>> processing /home/hartmut/octave/signal-1.3.2/fracshift.m
***** test
...
!!!!! test failed
'upfirdn' undefined near line 110 column 11


>>>>> processing /home/hartmut/octave/signal-1.3.2/fwht.m
***** assert (fwht (zeros (16)), zeros (16));
!!!!! test failed
'__fwht__' undefined near line 88 column 9


When I try the test procedure from comment #5 I also get the same result:
"PASS   454, FAIL  48, XFAIL  1".

So my original observation seems to stay valid (on my Ubuntu system): Octave
4.0.3 does not find the compiled package oct-files any more. 

When I do "pkg load signal, test fwht" in Octave 4.0.3 I get "...!!! test
failed... __fwht__ undefined", when I do the same command in Octave 4.0.1 I
get "PASSES 14 out of 14 tests".

The root cause may be:
* In Octave 4.0.3 the path functions gives me a list that contains
".../octave/signal-1.3.2" but NOT
".../octave/signal-1.3.2/x86_64-unknown-linux-gnu-api-v50+".
* In Octave 4.0.1 the path functions gives me both above mentioned paths.

Note: The ".../octave/signal-1.3.2/x86_64-unknown-linux-gnu-api-v50+" part is
the very first entry in my Octave search path. Somehow it got chopped off in
Octave 4.0.3!

Can someone else have a look at the output of "path" in Octave, if it seems
that the first line is chopped off? Normally each loaded package should have
the package folder there, as well as the subfolder with the compiled oct-files
(if it has any). I first observed the problem with the image package
(de-installing and installing removed the problem). And now I have this
problem with the signal package (I have not de-installed and re-installed,
yet).

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?48601>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/