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 23:13:16 +0200 Lines: 12 Message-ID: References: <46F6C151 DOT 3070301 AT computer DOT org> <20070929205512 DOT GB22223 AT ednor DOT casa DOT cgf DOT cx> 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: <20070929205512.GB22223@ednor.casa.cgf.cx> 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 Christopher Faylor wrote: > On Sat, Sep 29, 2007 at 10:20:23PM +0200, Diego Biurrun wrote: > >>llrint is required, so I guess Cygwin compilation will indeed be broken for >>a while. We don't add OS-specific workarounds to FFmpeg. > > So what other kinds of workarounds do you add? Workarounds for broken variants of the many multimedia formats we support for example. 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/