X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Thu, 10 Mar 2011 10:26:14 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Bug? LLVM builds fail on 1.7.8 (fenv.h) Message-ID: <20110310092613.GW12899@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Mar 9 17:47, Magnus Reftel wrote: > Hi all, > > it seems that the fenv.h introduction may have caused some problems. > LLVM fails to build now, and fit seems to me that it could be because > #define _GLIBCXX_HAVE_FENV_H 1 > is missing in > /usr/lib/gcc/i686-pc-cygwin/4.3.4/include/c++/i686-pc-cygwin/bits/c++config.h > > For the analysis, please see LLVM bug 9436 at > http://llvm.org/bugs/show_bug.cgi?id=9436 This isn't a Cygwin bug, but a bug in LLVM. How on earth can anybody expect that a define _GLIBCXX_HAVE_FENV_H is set on a system which doesn't even *use* glibc? The right thing to do for LLVM would be to add a autoconf test to check for fenv.h and then use HAVE_FENV_H instead of realying on a system-dependent define in one of the compiler headers. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple