X-Spam-Check-By: sourceware.org Message-Id: <6.2.3.4.2.20060821153350.0a0dbe30@pop.nycap.rr.com> X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4 Date: Mon, 21 Aug 2006 15:57:29 -0400 To: Dave Korn , cygwin AT cygwin DOT com From: "William A. Hoffman" Subject: RE: change in behavior of make from 3.80 to 3.81 In-Reply-To: <003d01c6c553$af945850$a501a8c0@CAM.ARTIMI.COM> References: <6 DOT 2 DOT 3 DOT 4 DOT 2 DOT 20060821135043 DOT 0a05b580 AT pop DOT nycap DOT rr DOT com> <003d01c6c553$af945850$a501a8c0 AT CAM DOT ARTIMI DOT COM> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk 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 At 02:57 PM 8/21/2006, Dave Korn wrote: >On 21 August 2006 18:58, William A. Hoffman wrote: > >> of, make is changing beware, it may have been noticed. Let's face make >> is not a project you expect to see a bunch of change happening on, >> especially a change that breaks existing makefiles. > > Ah. We have the nub of it. No I don't think you have the nub of it yet. I still think that a simple post about a major change being made to make may have helped avoid much of the pain of this thread. You have to admit that dropping a whole class of paths from support is more likely to cause trouble than any of the other minor syntax changes to gnu make that are not backwards compatible. I would not expect: foo: foo.c gcc foo.c -o foo To stop working any time soon in make no matter what changes are made. The basic format of makefiles is pretty much fixed, and has been around for 20 years or so. See http://en.wikipedia.org/wiki/Make: "POSIX includes standardization of the basic features and operation of the make utility " That is the part of make I am talking about when I say the features of make are not changing. I and others (not exactly sure how many but more than one) did not expect: foo: c:/foo.c cl c:/foo.c to stop working the make that came with cygwin. And in the future it will again be supported. I certainly realize that software changes, and that you have to break backwards compatibility from time to time. I am just saying that giving the user community an opportunity to step up and make a fix would have been helpful, not necessary or required, but helpful and not that hard to do. -Bill -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/