Re: cant find mkoctfile.

[Dmitri A. Sergatskov]

On Mon, Jul 2, 2018 at 1:38 AM, Andreas Weber <address@hidden> wrote:

Am 01.07.2018 um 23:09 schrieb Dmitri A. Sergatskov:
> I usually do (as root):
> cd /usr/local
> find ./ -name "*oct*" | xargs rm -rf

If you want to do that I would suggest to use
find ./ -name "*oct*" -delete

because it processes directories from depth first (so you don't get
errors if a directory already was deleted)

-- Andy

​It looks to me it is the other way around:

​find ./ -name "*oct*" -delete
find: cannot delete ‘./include/octave-4.4.0+/octave’: Directory not empty
find: cannot delete ‘./include/octave-4.4.0+’: Directory not empty
find: cannot delete ‘./share/octave/4.4.0+/etc/tests/libinterp/octave-value’: Directory not empty
find: cannot delete ‘./share/octave/4.4.0+/etc/tests/liboctave’: Directory not empty
find: cannot delete ‘./share/octave’: Directory not empty
find: cannot delete ‘./libexec/octave’: Directory not empty
find: cannot delete ‘./lib/octave/4.4.0+/oct’: Directory not empty
find: cannot delete ‘./lib/octave/4.4.0+/site/oct’: Directory not empty
find: cannot delete ‘./lib/octave/site/oct’: Directory not empty
find: cannot delete ‘./lib/octave’: Directory not empty

And I have never seen any errors/warnings with

find ./ -name "*oct*" | xargs rm -rf

​Dmitri.

--

​