X-Spam-Check-By: sourceware.org Message-ID: <43D74ADA.20606@verysmall.org> Date: Wed, 25 Jan 2006 10:54:34 +0100 From: "pobox@verysmall.org" User-Agent: Thunderbird 1.6a1 (Windows/20060119) MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Errors compiling cdrtools under cygwin 1.5.19 References: <012420061825.2204.43D671090006A0AD0000089C22092299270A050E040D0C079D0A@comcast.net> <20060124183552.GA2889@trixie.casa.cgf.cx> <43D69F82.8050209@verysmall.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com > I like this slogan: "Cygwin: nice, but not reliable". We should adopt > this, and refer 90% of the mailing list complaints to it. :-) > Igor I am not really sure how to understand the joke. cygwin worked flawlessly for me for very long time. May be I have been lucky, but this made me develop an attitude of blind trust in cygwin. Then came this 'getline' problem and what is confusing is not that things broke, but the reaction of the cygwin people. What I saw is that it is possible that cygwin breaks from one day to the next in critical area, and the reaction will be that everything that breaks is at its own fault. The problem is that if Apache have not fixed their 'getline' since 2002, it is very likely that they will not fix it soon, if at all. cygwin has quite a marginal place in comparison to all other operating systems they should address, an cygwin should be - due to this - a bit more careful when challenging the word. At least for me with cygwin is over. Iv. -- 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/