delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2006/08/16/13:43:57

X-Spam-Check-By: sourceware.org
Date: Wed, 16 Aug 2006 13:44:06 -0400
From: Bob Rossi <bob_rossi AT cox DOT net>
To: cygwin AT cygwin DOT com
Subject: Re: change in behavior of make from 3.80 to 3.81
Message-ID: <20060816174406.GA7538@brasko.net>
Mail-Followup-To: cygwin AT cygwin DOT com
References: <6 DOT 2 DOT 3 DOT 4 DOT 2 DOT 20060815151104 DOT 0b40e260 AT pop DOT nycap DOT rr DOT com> <01b901c6c116$21259430$a501a8c0 AT CAM DOT ARTIMI DOT COM> <6 DOT 2 DOT 3 DOT 4 DOT 2 DOT 20060816091525 DOT 0ab90af0 AT pop DOT nycap DOT rr DOT com> <20060816144110 DOT GX20467 AT calimero DOT vinschen DOT de>
MIME-Version: 1.0
In-Reply-To: <20060816144110.GX20467@calimero.vinschen.de>
User-Agent: Mutt/1.5.11
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

> > - have the patch made part of the upstream gnu make
> 
> That's the best solution of all.  The whole "problem" is that the
> current Cygwin make maintainer has no fun to work on this issue.
> Everybody else is free to put a bit of time and sweat into this and get
> this for free firther on.  I'm still wondering why people don't go this
> way instead of discussing this problem, which is none, IMHO, to death.

I agree with Corinna here, and others that have said it. There is a list
of us that find this patch useful. We should determine what the effort
would be to get this patch in the upstream source. Does anyone have time
for this right now?

Corinna, I can speak for myself, the reason this issue is discussed to
death is because of the reaction from the Cygwin people. Free software
users have an implicit association with friendly communication with the
software developers. In this instance, the cygwin maintainers (or higher 
ups) are pretty much belittling there users and/or saying there is no 
problem.  To many of us, there is a problem. 

I think your solution is well stated. Does anyone know who was 
maintaining the old patch to make, so that a discussion with that person 
could be made more substantial on a technical level?

Bob Rossi

--
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/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019