[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #30341] Cannot run 'test COMPILED_FUNCTION_NAM
[Octave-bug-tracker] [bug #30341] Cannot run 'test COMPILED_FUNCTION_NAME' from installed Octave
Thu, 08 Jul 2010 01:44:11 +0000
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:184.108.40.206) Gecko/20100407 Ubuntu/9.10 (karmic) Firefox/3.6.3
Update of bug #30341 (project octave):
Category: None => Configuration and Build
Item Group: None => Other
Status: None => Confirmed
Summary: Cannot run tests from installed Octave => Cannot
run 'test COMPILED_FUNCTION_NAME' from installed Octave
Follow-up Comment #1:
This issue is confirmed on a recent tip, but goes back at least as far as
The problem exists for all the compiled functions in
/usr/libexec/octave/VERSION/oct/ARCHITECTURE/. There are quite a few
functions here: eigs, inv, lsode, etc.
The issue is that test.m needs to find the test code and it looks for .m and
.cc files. If you have the development version you have the original source
code and the .cc files include the tests.
I'm not sure what the best solution is. We could have .m files which only
have the tests and the documentation strings and call the compiled function by
a different name. There are already examples of this I believe.
On the other hand, one usually verifies a build before installation and not
after. Running 'make check' will work because the source code is available.
I'm not sure how necessary it is to run 'test chol' after installing.
Reply to this item at:
Message sent via/by Savannah