On Tue, Jun 05, 2012 at 08:41:39PM -0700, Bryan Kadzban wrote: > > That doesn't explain why it gets run in this particular case though. > We're editing configure, which should set its mtime to "right now", > which should be later than configure.ac. Unless configure.ac is > shipping with an mtime in the future? > > We don't sed aclocal.m4, so that's not the issue... > > AHA! configure.ac is shipped newer than aclocal.m4, so aclocal gets > run, which causes automake and autoconf to both be required. This would > have happened whether or not we did any patching or anything. To stop > it from running entirely, we could also teach a new syntax for touch, > and: > > touch -d '2011-05-07 13:30' configure.ac > > at any point during the configuration (during patching or sedding or > whatever), although that will only work for the current kbd release. >
Thanks for explaining it properly. I have two problems with fixing it: 1. It may encourage the people who are resurrecting the "drop autotools from LFS" suggestion :) 2. How did you decide on that date and time ? In a just untarred kbd tree, with configure touched to simulate an update, in UTC+1 I get root in chroot /building/kbd-1.15.3# ls -l --time-style=long-iso \ configure* aclocal.m4 -rw-r--r-- 1 ken 500 36173 2011-05-07 21:32 aclocal.m4 -rwxr-xr-x 1 ken 500 263199 2012-06-07 00:08 configure -rw-r--r-- 1 ken 500 2099 2011-05-14 22:37 configure.ac Your touch works, but I'd like to understand why, and therefore to be sure it will also work for people in all timezones (apparently, a range of -10 to +14, or from -12 if the military timezones actually exist). ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
