X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Diego Biurrun Subject: Re: llrint implementation in Cygwin Date: Sat, 29 Sep 2007 21:14:42 +0200 Lines: 50 Message-ID: References: <46F6C151 DOT 3070301 AT computer DOT org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.8b) Gecko/20050217 In-Reply-To: X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Igor Peshansky wrote: > On Fri, 28 Sep 2007, Diego Biurrun wrote: > >>Tim Prince wrote: >> >>>Diego Biurrun wrote: >>> >>>>I have noticed that Cygwin does not implement llrint. However, >>>>llrint is part of C99 and not having it available makes some >>>>applications (for example MPlayer and FFmpeg) fail to compile. >>>> >>>>Are there any plans to implement llrint (in the near future)? >>> >>>Perhaps if you would submit a patch to newlib, something may happen. >> >>Telling me what newlib is would greatly help in this regard :-) > > Newlib is the library that Cygwin uses for some standard functions (math > and otherwise). > > (The only way to interpret this question is "what is the connection > between newlib and Cygwin", as a quick Google would have pointed you to > the newlib webpage). Yes, I was not precise. I was unsure about the relationship between Cygwin and newlib. >>I understand that adding llrint to Cygwin is probably not hard at all >>for somebody familiar with Cygwin. However, I am not such a person and >>I don't even have a Windows environment around to test any modifications >>I might make. >> >>We are about to make an MPlayer release and unfortunately it will not >>compile on Cygwin due to the missing llrint. I would appreciate to know >>if this is going to get addressed so that I can put an appropriate >>comment in the release notes. > > What's wrong with adding llrint to your code (perhaps with a #define, > i.e., > > #define llrint my_llrint > typeof(llrint) my_llrint(...) { ... } > > )? It is ugly and it is a workaround for a problem that should be solved outside of FFmpeg. Should every project using llrint add that workaround? No, Cygwin should be fixed. Diego -- 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/