X-Spam-Check-By: sourceware.org Message-ID: <442C2D03.7050302@mycom-int.fr.invalid> Date: Thu, 30 Mar 2006 21:09:55 +0200 From: Shaddy Baddah Reply-To: sbaddah AT mycom-int DOT fr DOT invalid, cygwin AT cygwin DOT com User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: GNU make 3.81rc2 available and I'm worried Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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 Hi, According to the announcement of GNU make 3.81 release candidate 2 (http://lists.gnu.org/archive/html/make-alpha/2006-03/msg00007.html), 3.81 is coming (or should of came last week), and I'm worried. I am worried that there isn't going to be a quick turn-around in getting a Cygwin build out. Before proceeding full on with why I am worried, I'll ask the question. Obviously there are no guarantees, but does the GNU make maintainer expect that is going to be easy enough to get out a Cygwin build soon after the official release? My worry that there will be a delay is two part. The first part... I downloaded GNU make 3.81rc2 and configured/built it out of the box. Good news it seems. The problem though is that there is a regression that causes the following error: mergespecrules.mk:14: *** target pattern contains no `%'. Stop. where make is confusing eval'ed as regular rules of the form: TARGETS : PREREQUISITES COMMAND because for whatever reason, it using the windows form of the paths like: merge.txt : c:/mergespecs/1/merge.txt c:/mergespecs/2/merge.txt mergecmd $@ $^ and the extra colons make make think they are "Static Pattern Rules" of the form: TARGETS ...: TARGET-PATTERN: PREREQ-PATTERNS ... COMMANDS Or that is the problem as I read it. Deeper analysis left out, this doesn't happen under linux or w32 builds, so it suggests to me that Cygwin builds need patches. The second part is, the last Cygwin GNU make, version 3.80, was on 6/21/2003, a long while ago now. And the patches I produced against the pristine 3.80 don't seem to have been included upstream into 3.81rc2. That suggests to me that someone is going to have to piece together the reasoning and merge the patches before making the Cygwin build. In any case, I'll be keeping my eye out, and if I have spare time, I will try and solve this problem myself. Would an experimental release be in order? Regards, Shaddy -- 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/