[Octave-bug-tracker] [bug #47424] Cannot run "test function" for builtin functions

[Lachlan Andrew]

Follow-up Comment #3, bug #47424 (project octave):

Thanks for the suggestions, Mike and Carnë.  The attached revision addresses
them.

It should now work if the source is build in the main source directory, as
well as built in .build.  (Mike, I assume the latter is what you meant by
"out-of-tree build".)  It also re-makes the .cc-tst file if the .cc file is
more recent.  (The make file does a grep followed by a mv, so I do the same. 
Do you know why not just do the grep to the final destination?  I would have
assumed the goal was an atomic replace of old by new, but the old file is
removed before the grep.)  If there are no tests, this should result in an
empty file, which I hope should avoid the "???? builtin" message.

If the .cc file can't be found, it uses the one in OCTAVE_HOME.  This will
give the "???? builtin" message if there are no tests.  It would also be the
wrong thing to do if the build is in a directory that isn't either the main
source directory or a child of that.  Is there a way to test whether we're
running  ./run-octave  rather than an installed version?

The has more possible code paths than the previous, and I'm not sure I've
tested them all yet.  I'll confirm once I have.

(file #36710)
    _______________________________________________________

Additional Item Attachment:

File name: bug_47424_test.cset            Size:2 KB


    _______________________________________________________

Reply to this item at:

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

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