On 2007-07-07 14:17:51 -0700, Ben Pfaff wrote: > Do you have a suggestion for how I might reproduce the problem on > a desktop system? If I can reproduce it, I can probably debug it.
I've now found the problem. This is unrelated to the use of "cp -p". On my Zaurus, GCC and some of header files are in a directory mounted with CRAMFS. The timestamps of these files are meaningless, e.g. -rwxr-xr-x 1 root root 808 Jul 9 14:30 exception* -rwxr-xr-x 1 root root 3360 Jan 1 1970 float.h* -rwxr-xr-x 1 root root 275 Jan 1 1970 iso646.h* -rwxr-xr-x 1 root root 3264 Jul 9 13:42 limits.h* -rwxr-xr-x 1 root root 1207 Jan 1 1970 new* -rwxr-xr-x 1 root root 161 Jan 1 1970 new.h* -rwxr-xr-x 1 root root 137 Jan 1 1970 proto.h* -rwxr-xr-x 1 root root 495 Jan 1 1970 readme* -rwxr-xr-x 1 root root 6038 Jul 9 13:41 stdarg.h* -rwxr-xr-x 1 root root 502 Jan 1 1970 stdbool.h* -rwxr-xr-x 1 root root 9834 Jul 9 13:40 stddef.h* -rwxr-xr-x 1 root root 330 Jan 1 1970 syslimits.h* [...] As such headers are listed in the .deps/*.Plo files, I probably get unnecessary rebuilds because of that. I wonder if it is possible to prevent such header files from appearing in these .deps/*.Plo files. -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: <http://www.vinc17.org/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/> Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)
