From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 0BEAB3856DD0; Thu, 11 May 2023 21:13:19 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0BEAB3856DD0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1683839600; bh=el2yc69feaJFXekx+ulAWvRyh91eaunGu2+Fnh+kdlg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=G/tWhSH/5JrnaLiIHMMhtSvbTXvovwmgssTkbR3lBwwUJaw6U8jJ8CG10T0vpx2HE Z7KxmSt17jqrUvRlYjL1HDPeJpb2SphwV6xvQ1dg7yML+w6KzJFXFWzzeb2VV5x1GM EFls9x5UY9Y3QISXVrn52L6VvK1htIXFpUYXDqLQ= From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/109818] std::trunc() requires a hack after building DJGPP Date: Thu, 11 May 2023 21:13:19 +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: 13.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- 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 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D109818 --- Comment #4 from Jonathan Wakely --- Hmm, I don't see anything in the configure scripts that would cause c_std t= o be used implicitly for djgpp (or any other target). Maybe there's a local patch applied to the djgpp copy of GCC sources? It might set C_INCLUDE_DIR explicitly, or adjust the default chosen for GLIBCXX_ENABLE_CHEADERS in libstdc++-v3/acinclude.m4=