From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 432E43858020; Sun, 7 Nov 2021 19:40:30 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 432E43858020 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: Sun, 07 Nov 2021 19:40:30 +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: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned 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: Sun, 07 Nov 2021 19:40:31 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D100017 --- Comment #40 from cqwrteur --- (In reply to Andrew Aladjev from comment #38) > Sure, patches works perfect. But we need somehow decrease the chance of > similar regressions in future. It is possible by adding any basic "canadi= an" > build into the list of tests to be done before release. We should not try= to > add such test into codebase itself, we need just to intrigue any of core = gcc > developers to add this test into the virtual checklist. >=20 > Thank you. Issues like this are exactly why i would never use a script (including thin= gs like cross-ng) to build anything. I would build everything manually since i= t is very likely to fail for all sorts of different reasons, neither their testi= ng would fix it since they have to include different libcs (we have hundreds of different libcs) to test each of them, which is not possible.=