On 10/31/2014 02:02 PM, David Roundy wrote:
I've just been struggling with fuse errors on my work computer, where
I wasn't originally a member of the fuse group, and I'm working on
nfs... I still haven't figured out which of these caused the most
errors, but things still aren't working. I expect that if tup is
packaged by Debian, many of these pains will go away.
However, I got to wondering if ptrace might serve. If all you need is
to trace syscalls, I think this could work on Linux anyhow. The
downside is that you'd need to make tup understand all system calls
that would affect files. The plus side would be that it would be much
simpler and more robust in operation, since you wouldn't have to mount
and unmount a fake filesystem, and it would work with statically
linked executables (including ones that don't use libc). The downside
is that you might not be able to lie about readdir's results to
convince executables that generated files don't exist.
Anyhow, just a few thoughts, after an hour or so of fruitless attempts
to make tup work.
David
Here is a post by Mike about different dependency tracking options -
there's also a chapter about ptrace().
http://gittup.org/blog/2014/05/7-clobber-builds-part-2---fixing-missing-dependencies/
What problems do you have? I've recently switched to Linux and I've
probably faced the same issues as you did, so maybe I'll be able to
help. I'm using Arch, so things may be a bit different.
Regards,
FCh
--
--
tup-users mailing list
email: [email protected]
unsubscribe: [email protected]
options: http://groups.google.com/group/tup-users?hl=en
---
You received this message because you are subscribed to the Google Groups "tup-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
