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 Date: Fri, 24 Oct 2003 15:27:43 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: undefined reference to `_getline' Message-ID: <20031024192743.GA7513@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <3D848382FB72E249812901444C6BDB1DE4DF11 AT exchange DOT timesys DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D848382FB72E249812901444C6BDB1DE4DF11@exchange.timesys.com> User-Agent: Mutt/1.4.1i On Fri, Oct 24, 2003 at 01:05:02AM -0400, Robb, Sam wrote: >>I suppose that in all of your searching you never came across the >>concept that cygwin uses newlib and that cygwin does not export every >>single thing from newlib? That means that there are some things >>defined in headers which are not actually available in cygwin. > >No, I understand that - I was wondering if the missing export is >becuase of a lack of interest, or if there is some problem with the >newlib version of getline() that keeps it from being exported. As a good net citizen if I was aware of a problem with getline in a package that I was associated with, I'd be attempting to get it fixed. Let me use another tried and true aphorism: patches thoughtf..., er, patches gr... Just submit a #(&*! patch, ok? Cheesh. cgf ***Note: The above was an attempt at humor. Please be advised. -- 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/