Fri 05 Aug 2016 06:56:49 PM UTC, original submission:
Forge packages that where installed under Octave 4.0.1 aren't fully functional under Octave 4.0.3. The reason seems to be a change in the "configured for" string between those two Octave version. (In my case this was "x86_64-unknown-linux-gnu-api-v50+" and changed to "x86_64-pc-linux-gnu-api-v50+".)
This was observed on a Ubuntu 14.04 linux system, both Octave versions are self compiled from the official release tar-balls.
Here is how to reproduce the behavior, with the example of the image package:
In Octave 4.0.1 do:
This will show the two paths of the image package:
- ~/octave/image-2.4.1
- ~/octave/image-2.4.1/x86_64-unknown-linux-gnu-api-v50+
Then in Octave 4.0.3 do:
- This will only show one of the necessary paths for the image package, the subfolder with the compiled oct-files is missing:
- ~/octave/image-2.4.1
The reason for this becomes obvious when you continue in Octave 4.0.3:
This will again show the two necessary paths:
- ~/octave/image-2.4.1
- ~/octave/image-2.4.1/x86_64-pc-linux-gnu-api-v50+
Note that the name of the oct-file subfolder is now DIFFERENT, it is "pc-linux" instead of "unknown-linux". This seems to be the reason for packages to not work properly under Octave 4.0.3 if they have been installed under Octave 4.0.1 (or earlier).
(Prior to this bug report, this was nailed down during bug #48601.)
This change in this "configured for" string might be an intended change and well known change during the development from Octave 4.0.3 to 4.0.1. But it does have the explained side effects.
I am fully aware of the possibility to "work around" this behavior, by simply re-installing all packages. But this might not be obvious for the other Octave users.
|