Hello list, Why are /usr/include files installed with "install -C" during "make installworld" when almost everything else is installed without the -C flag? This makes it harder to track which files were actually installed during the last "make installworld". One can easily find obsolete files (that are not covered with make delete-old(-libs)) with "find -x / -type f -mtime +suitable_time" but this doesn't work for /usr/include files because the modification times are not bumped on "make installworld".
Kimmo Paasiala <kpaasial@gmail.com> writes:> Why are /usr/include files installed with "install -C" during "make > installworld" when almost everything else is installed without the -C > flag? This makes it harder to track which files were actually > installed during the last "make installworld". One can easily find > obsolete files (that are not covered with make delete-old(-libs)) > with "find -x / -type f -mtime +suitable_time" but this doesn't work > for /usr/include files because the modification times are not bumped > on "make installworld"."make" uses timestamps to determine whether to trigger a rule. Changing timestamps on source files without changing the contents is a bad idea.
Christer Solskogen
2012-Jun-04 07:11 UTC
Installworld and /usr/include/*.h modification times
On Fri, Jun 1, 2012 at 3:42 PM, Kimmo Paasiala <kpaasial@gmail.com> wrote:> Hello list, > > Why are /usr/include files installed with "install -C" during "make > installworld" ?when almost everything else is installed without the -C > flag? This makes it harder to track which files were actually > installed during the last "make installworld". One can easily find > obsolete files ?(that are not covered with make delete-old(-libs)) > with "find -x / -type f -mtime +suitable_time" but this doesn't work > for /usr/include files because the modification times are not bumped > on "make installworld". >If you want, you can do this /after/ a buildworld # mv /usr/include /usr/include.old # cd /usr/src # make hierarchy # make installincludes -- chs,