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: <5.1.0.14.2.20021121143225.02ac95f0@pop3.cris.com> X-Sender: rrschulz AT pop3 DOT cris DOT com Date: Thu, 21 Nov 2002 14:43:07 -0800 To: cygwin AT cygwin DOT com From: Randall R Schulz Subject: Re: old cygwin distributions In-Reply-To: <10823177609.20021121232447@huno.net> References: <022101c291aa$97665890$78d96f83 AT pomello> <7916445640 DOT 20021121213235 AT huno DOT net> <01c901c291a1$476f16a0$78d96f83 AT pomello> <1119233000 DOT 20021121221902 AT huno DOT net> <022101c291aa$97665890$78d96f83 AT pomello> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Thomas, While bug reports are appreciated and necessary, the ball remains in your court. If you wait for someone else to address the problem, you may wait a long time. This is especially true since you're using software that has no Cygwin maintainer. Have you consulted with the development team for "cdrecord?" If you do some of the diagnostic leg work and report your results here, you're much more likely to get the attention of someone with a meaningful insight leading to a resolution of the problem. Tools of choice here are gdb and strace, I'd say. Randall Schulz Mountain View, CA USA At 14:24 2002-11-21, thomas wrote: >Max Bowsher wrote: > > > Well, theoretically, you could rebuild an older version from cvs. But it > > would probably be easier to help track down the bug and get it fixed. > >Oh, I am more than willing to help. [It's] just that no one replied to my >bug report yet :) > >thomas -- 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/