X-Spam-Check-By: sourceware.org Message-ID: <46566982.7000006@qualcomm.com> Date: Thu, 24 May 2007 21:43:46 -0700 From: Rob Walker User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: make-3.81 update? References: <46565CBE DOT 7020401 AT qualcomm DOT com> <20070525041200 DOT GA14393 AT ednor DOT casa DOT cgf DOT cx> In-Reply-To: <20070525041200.GA14393@ednor.casa.cgf.cx> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Christopher Faylor wrote: > On Thu, May 24, 2007 at 08:49:18PM -0700, Rob Walker wrote: > >> http://cvs.savannah.gnu.org/viewcvs/make/job.c?rev=1.182&root=make&view=auto >> >> Looks like the Windows-style paths support has been accepted as an >> upstream patch. When can Cygwin pick this up? >> > > It is very much not a priority. I'll probably wait for the next release > of make. The CVS version has some reported bugs anyway. > Thanks for the update. What might make this a priority? My situation is this: I cannot advocate an off-the-rack Cygwin installation for my team or my customers. My current choices are: 1. supply an in-house compiled Cygwin version of make-3.81 (without cygwin1.dll, of course) that has the patch, with installation instructions and caveats 2. supply an old Cygwin make-3.80 (with similar instructions and /more/ caveats) 3. tell my customers and team to "figure it out" Is the CVS version with its bugs worse (calls for some subjectivity) than the current Cygwin make-3.81-1? Are the bugs new since 3.81-1? Can Cygwin take *just* the "colon in paths" patch? I'm happy to help any way I can. Thanks, Rob -- 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/