Hello Ilya, thanks for the report.
* Ilya N. Golubev wrote on Thu, Aug 21, 2008 at 08:15:32PM CEST: > > This seems like an automake question, not a make question. > > Confirming it to be so: (it is the bug described in) > <[EMAIL PROTECTED]> (posted) to <bug-automake@gnu.org> on Wed, > 20 Aug 2008 22:43:38 +0400. So moving the discussion from > <[EMAIL PROTECTED]> here. That initial report is here: <http://thread.gmane.org/gmane.comp.gnu.make.bugs/3831> I'm afraid I don't fully understand the nature of the bug, from reading that report, so this is asking for clarification. Please note that your readers may have a different context, so some things that may be obvious to you are not to me for example. There may also be some language barrier, so it's really helpful if we stick to commands and command output to precisely see what we do and what happens. Here's what I tried to reproduce the issue you reported: I took a pristine coreutils source tree, in coreutils/. Then I mkdir build cd build ../coreutils/configure make Then, to reproduce your bug, I tried this: rm -f ../coreutils/Makefile.in make ../coreutils/Makefile.in The full output of the last command was: | cd ../coreutils && /bin/sh /tmp/coreutils/coreutils/build-aux/missing --run automake-1.10 --gnu | cd . && /bin/sh ./config.status Makefile | config.status: creating Makefile | make: `../coreutils/Makefile.in' is up to date. It seems to work as expected. I tested on an x86 GNU/Linux system, with Autoconf 2.62, Automake 1.10.1, and GNU make 3.81. Now, what's different for you, or what did you do differently, in order to encounter the bug? Cheers, Ralf