This result indicates that the utime system call with a null second argument doesn't work as it should on your system. It's probably a kernel problem, unless your build has something other than the syscall for utime. I can't reproduce this on my system (debian ppc sid), both with a local build directory and one that's on NFS.