Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Message-ID: <20020714153752.37420.qmail@web21009.mail.yahoo.com> Date: Sun, 14 Jul 2002 08:37:52 -0700 (PDT) From: Nicholas Wourms Subject: Re: cygwin cvs question To: Joshua Daniel Franklin , cygwin AT cygwin DOT com In-Reply-To: <20020714152734.43380.qmail@web20003.mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii --- Joshua Daniel Franklin wrote: > OK for some reason I decided to update to the exp gcc-3.1.1-2 etc. > (cygcheck > attached) > packages and then rebuild cygwin from CVS. Things seemed to be > working fine other than more warnings than before from libiberty > until make got to newlib/libc/search/Makefile, when it said no target > for all. I looked and the Makefile was empty. The > src/newlib/libc/Makefile.* > files looked fine. > > So I thought what the heck, moved by src and bld trees and re-ran > cvs co winsup. The build is running now and seems to be fine--it created > newlib/libc/search/Makefile fine and has already made (make'd?) libc.a > So my question is, did I need to do something other than just 'cvs > update' > to catch changes like that? What happened was they modified the Makefile.in's/Makefile.am's so you should rerun config.status in any of the directories you notice this happening in. For good mesure, I usually just wipe that particular directory in my build tree when I notice a change in Makefile.in/Makefile.am/configure. The way it is supposed to work is that make detects the change and will automatically rerun config.status. Howerver this can hardly be depended on. Cheers, Nicholas __________________________________________________ Do You Yahoo!? Yahoo! Autos - Get free new car price quotes http://autos.yahoo.com -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/