2008/11/25 Ted Gould <ted@...11...>:
$ ls -al filters/.deps/.dirstamp ls: cannot access filters/.deps/.dirstamp: No such file or directory
Hmm, that's odd. But the file is really only there to mark when the directory was last read. It would seem that:
touch filters/.deps/.dirstamp
Would fix the problem, but I have no idea why it happened.
$ touch src/filters/.deps/.dirstamp touch: cannot touch `src/filters/.deps/.dirstamp': Permission denied
$ ls -lh src/filters/.deps/ total 80K -rw-r--r-- 1 root root 8 Nov 25 16:36 blend.Po
etc.
All files have root access permission. I'm quite puzzled. These are really two different machines with two different checkouts, and the last successful build was surely after November 8, just like the one for the laptop at home.
Alexandre
On Tue, 2008-11-25 at 18:12 +0300, Alexandre Prokoudine wrote:
2008/11/25 Ted Gould <ted@...11...>:
$ ls -al filters/.deps/.dirstamp ls: cannot access filters/.deps/.dirstamp: No such file or directory
Hmm, that's odd. But the file is really only there to mark when the directory was last read. It would seem that:
touch filters/.deps/.dirstamp
Would fix the problem, but I have no idea why it happened.
$ touch src/filters/.deps/.dirstamp touch: cannot touch `src/filters/.deps/.dirstamp': Permission denied
$ ls -lh src/filters/.deps/ total 80K -rw-r--r-- 1 root root 8 Nov 25 16:36 blend.Po
etc.
All files have root access permission. I'm quite puzzled. These are really two different machines with two different checkouts, and the last successful build was surely after November 8, just like the one for the laptop at home.
My guess: Russian hackers ;)
More realistic: You probably did a 'make install' as root and it wasn't fully up-to-date so the root user built some things. Now your local user can't update those files. If find the best solution here is to blow away the build (as root) and start over. But, probably a "chown -R aprokoudine *" would work also.
--Ted
participants (2)
-
Alexandre Prokoudine -
Ted Gould