From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30461 invoked by alias); 2 Sep 2010 08:24:13 -0000 Received: (qmail 30345 invoked by uid 48); 2 Sep 2010 08:23:50 -0000 Date: Thu, 02 Sep 2010 08:24:00 -0000 Message-ID: <20100902082350.30344.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug libstdc++/40974] [4.3/4.4/4.5/4.6 Regression] cannot build gcc-4.4.1: fenv_t has not been declared In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "boris at kolpackov dot net" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2010-09/txt/msg00188.txt.bz2 ------- Comment #44 from boris at kolpackov dot net 2010-09-02 08:23 ------- I just ran into the same issue building (native) mingw32 GCC 4.5.1 using a x86-64 to mingw32 cross compiler. Adding -nostdinc++ to PCHFLAGS fixed this for me as well. I also would like to point out that when building in this configuration the target libraries (libgcc, libstc++) are built using the cross-compiler. Since these libraries are internal to GCC (and can theoretically track the GCC version), I think it is reasonable to expect that the cross and native compilers are the exact same version of GCC. Using different versions in this setup is just asking for trouble. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40974