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: <46935.213.38.17.50.1041869937.squirrel@raq299.uk2net.com> In-Reply-To: <20030106155840.GC25858@redhat.com> References: <20030106065320 DOT E6109407C AT sitemail DOT everyone DOT net> <20030106155840 DOT GC25858 AT redhat DOT com> Date: Mon, 6 Jan 2003 16:18:57 -0000 (GMT) Subject: Re: Re: help for compiling problem! From: "Dave Hooper" To: cygwin AT cygwin DOT com MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 Importance: Normal >>>error: main.c: undefined reference to '_setlinebuf' >> > cygwin doesn't provide setlinebuf. > In general what this means is that you have to actually "inspect" the > code and "port it" As a follow up to this, and the earlier thread regarding icmp (which presumably is resolved in the same way), would it not be "better" to add support for the icmp function and setlinebuf to cygwin? "Better" in the sense that Crystal is better than Moet - and I'm not suggesting everyone ought to be able to afford Crystal. Is there any technical reason why support cannot be added to Cygwin for these (and other) unprovided functions? Is there a canonical list of what people expect cygwin to support vs. what it actually supports, and hence what it currently lacks? d -- 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/