On 16/05/11 20:47, Ralf Wildenhues wrote:
> Hi Pádraig,
> 
> * Pádraig Brady wrote on Mon, May 16, 2011 at 04:44:42PM CEST:
>> On 14/05/11 09:07, Paul Eggert wrote:
>>>> If something treats symlink mtime as significant,
>>>> then I suspect that it's at fault.
>>>
>>> Yes, there's something busted there.  GNU 'make' does the right thing:
>>> it follows symlinks when checking time stamps.  Is some other 'make'
>>> is being used, or perhaps some tool other than 'make'?
>>
>> I suspect something else in the depths of auto* is busted,
>> as I'm using standard make.
> 
> GNU make, I presume.
> 
> Is this issue still open?  And if yes, how can it be reproduced?
> (Sorry, I haven't been following the thread really, but I still
> can't let a non-bug-report without details go uncommented.  ;-)

Sorry I have no time to dig into this currently.
I know I'd lose half a hour (it's on my ever increasing todo list).

Anyway fa6f0000 from gnulib broke my coreutils build dir,
because @HAVE_SIGHANDLER_T@ was not replaced.
I've noticed before that if I remove the symlinks
from the m4 directory and rerun bootstrap,
then things start working.

cheers,
Pádraig.

Reply via email to