X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-0.9 required=5.0 tests=AWL,BAYES_00,DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED,SPF_HELO_PASS,T_RP_MATCHES_RCVD,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By:	sourceware.org
Message-ID:	<28468326.post@talk.nabble.com>
Date:	Wed, 5 May 2010 18:15:02 -0700 (PDT)
From:	MichaelKim <souren AT gmail DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Cygwin make target is never determined up to date
In-Reply-To:	<4BE21AAC.5030704@gmail.com>
MIME-Version:	1.0
References:	<28454344 DOT post AT talk DOT nabble DOT com> <4BE0F722 DOT 1040009 AT bopp DOT net> <28456659 DOT post AT talk DOT nabble DOT com> <4BE0FC52 DOT 80708 AT bopp DOT net> <4BE11A07 DOT 1040308 AT gmail DOT com> <28467628 DOT post AT talk DOT nabble DOT com> <4BE20556 DOT 8040705 AT gmail DOT com> <28467801 DOT post AT talk DOT nabble DOT com> <4BE20D67 DOT 3040707 AT gmail DOT com> <28467975 DOT post AT talk DOT nabble DOT com> <4BE2135A DOT 2080903 AT gmail DOT com> <28468153 DOT post AT talk DOT nabble DOT com> <4BE21AAC DOT 5030704 AT gmail DOT com>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

Well, it's confusing because I have 3 machines.

1. WinXP (cygwin 1.5.19) - once built, the timestamps are equal and no
problem( happy with that, but I got the point that this is wrong makefile
design)

2. Win7 (cygwin 1.7.5) - once built, the timestamps are equal, and no
further build required if files are intact. However, sometimes the
timestamps are not equal and it doesn't consider targets up to date.

3. Another Win7 (cygwin 1.7.5, I can check exactly later) - timestamps are
always different, hence it's NEVER up to date. This is the original case I
was talking about.

Hope it's clear now.

Sorry for misleading and confusing you ^^


Dave Korn-6 wrote:
> 
> On 06/05/2010 01:45, MichaelKim wrote:
>> Just to make sure  we are on the same page.. Whenever the timestamps are
>> equal, it doesn't consider target as out of date, hence nothing happens.
> 
>   Heh, it's as well you said that, I had it the wrong way around.  I'm not
> clear now: the subject says 'never' up to date, but do you also mean that
> sometimes it gets it right anyway?  That would be strange.
> 
>     cheers,
>       DaveK
> 
> 
> 
> --
> Problem reports:       http://cygwin.com/problems.html
> FAQ:                   http://cygwin.com/faq/
> Documentation:         http://cygwin.com/docs.html
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> 
> 
> 

-- 
View this message in context: http://old.nabble.com/Cygwin-make-target-is-never-determined-up-to-date-tp28454344p28468326.html
Sent from the Cygwin list mailing list archive at Nabble.com.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -