From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12758 invoked by alias); 15 Dec 2009 20:48:53 -0000 Received: (qmail 12168 invoked by uid 48); 15 Dec 2009 20:48:36 -0000 Date: Tue, 15 Dec 2009 20:48:00 -0000 Message-ID: <20091215204836.12167.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug libstdc++/40974] 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: "armand dot potter at free dot fr" 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: 2009-12/txt/msg01520.txt.bz2 ------- Comment #13 from armand dot potter at free dot fr 2009-12-15 20:48 ------- I'm using about the same configuration (cross-LFS build but with gcc 4.4.2) and got the same error. I did some investigations and the problem is that fenv.h file from build tree is first included (and defines _GLIBCXX_FENV_H to 1) and then include_next includes fenv.h from host (installed in /usr/TARGET/include/c++/VERSION/fenv.h) and this time as _GLIBCXX_FENV_H is already defined, does nothing so fenv.h from glibc is never included. For a native build, just compiled c++ compiler is used with the -nostdinc++ flag so that /usr/TARGET/include/c++/VERSION/fenv.h is not seen and include_next works as expected including glibc header. I don't know what is the correct solution but at least you know what the real problem is. ~ -- armand dot potter at free dot fr changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |armand dot potter at free | |dot fr http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40974