From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id DC358385801B; Thu, 6 Jan 2022 18:08:50 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DC358385801B From: "unlvsur at live dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/100017] [11/12 regression] error: 'fenv_t' has not been declared in '::' -- canadian compilation fails Date: Thu, 06 Jan 2022 18:08:50 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 11.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: normal X-Bugzilla-Who: unlvsur at live dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: redi at gcc dot gnu.org X-Bugzilla-Target-Milestone: 11.3 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jan 2022 18:08:51 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D100017 --- Comment #65 from cqwrteur --- (In reply to Jonathan Wakely from comment #62) > But that's off topic for GCC's bugzilla, please try to focus. Is that because #if _GLIBCXX_HAVE_FENV_H # include #endif here _GLIBCXX_HAVE_FENV_H in the libstdc++ build scripts fails to detect fenv.h? What about replacing it with #if __has_include() ? (In reply to Alexander von Gluck from comment #64) > (In reply to cqwrteur from comment #61) > > TBH, I failed to see how cross-compile in llvm is simple compared to GC= C. >=20 > I mean... bootstrap. Compiling Canadian toolchains to compile non-Canadi= an > toolchains is a pretty difficult task. It's a big reason the BSD's went > clang. >=20 > *ANYWAY* wasn't looking to start a holy war.. just point out that Canadian > builds in gcc are important and should likely have a few base tests. >=20 > (In reply to Jonathan Wakely from comment #62) > > But that's off topic for GCC's bugzilla, please try to focus. >=20 > Indeed. Back on topic, the patchset listed definitely does solve the is= sue > for us. I didn't commit it to our gcc fork (that we plan on working to > upstream for Haiku support) though since a final iteration wasn't decided= / > committed yet here. Difficult? hmmm. Even middle school kids could easily do this. I guess nowadays people just randomly search things on the internet for wro= ng sources and rely on the things like cross-ng that adds difficulties to it. = In fact cross-ng just makes simple things hard not simple. I am against all these auto build scripts. They just make simple things hard and constantly break for all sorts of reasons.=