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: <28468372.post@talk.nabble.com> Date: Wed, 5 May 2010 18:23:16 -0700 (PDT) From: MichaelKim To: cygwin AT cygwin DOT com Subject: Re: Cygwin make target is never determined up to date In-Reply-To: <4BE21D9B.9010302@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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> <28468326 DOT post AT talk DOT nabble DOT com> <4BE21D9B DOT 9010302 AT gmail DOT com> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com You've got my point and I'll report the exact dll version later today. However, I redesigned the makefile in order to avoid such bad dependency. Dave Korn-6 wrote: > > On 06/05/2010 02:15, MichaelKim wrote: >> 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. > > Yes, I see; so the thing we need to understand (from posix compatibility > point of view) is why on the first win7 machine, the timestamps are not > /always/ unequal! > >> Sorry for misleading and confusing you ^^ > > No need to apologise, I spend most of my life confused, it's only when I > get > too certain that I really know something that I may make a mistake :) > > 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-tp28454344p28468372.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