octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: file-io.cc-tst failures


From: Michael D. Godfrey
Subject: Re: file-io.cc-tst failures
Date: Wed, 13 Nov 2013 11:09:58 -0500
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0

On 11/13/2013 10:50 AM, Rik wrote:
You have left-over cruft on your system.  There used to be %!tests in
file-io.cc and so Octave would generate a file-io.cc-tst file.  But, those
tests were removed.  The simplest way to get a clean tree is to hg clone a
new copy.  I often have lots of small projects and files that I am working
on so I don't use hg clone.  Instead, to avoid the cruft build-up I
periodically weed the directory tree.  Try 'hg stat -u > u.list' which will
produce a list of files which are not under Mercurial control, and then
delete any that don't belong to you.  I also do 'hg stat -i > i.list' from
time to time because certain suffixes, like .o, are ignored rather than
unknown.  When the build system changes a lot, as it has been doing, you
often end up with orphaned object files.

--Rik
Rik,

This is good advice, and this problem seems to happen quite often. So,
could I suggest hat a similar statement should go somewhere in Appendix G
of the Manual?  Maybe G.4?

Michael



reply via email to

[Prev in Thread] Current Thread [Next in Thread]