From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 1F036385C6C1; Sat, 13 Jul 2024 12:57:31 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1F036385C6C1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1720875451; bh=wgELdS97FJunrb901MlFmz+zUL6ynNKQqLsATV/Y3AA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=UVRa+S3mUkPcIAuC897eIIiWK0t8ymZgQszaOK7oPmsWNWK3YRdADsMwr9r1PVWiZ dmPGaxT8vn685t1C9yJycKsbAQDa9eBaygvQ+HjN6Qm7lajQ6IOq6uULRIdc2GQ4we ArKTnHPG5SfBQ9wsFHG039ayduHkXAk+wZz6QkJY= From: "unlvsur at live dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/115907] Libstdc++ and GCC itself should avoid glibc above 2.34 dependency Date: Sat, 13 Jul 2024 12:57: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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: unlvsur at live dot com 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=3D115907 --- Comment #5 from cqwrteur --- (In reply to Andrew Pinski from comment #3) > Note while glibc is backwards compatibility, it is not forward compatible. > So if you build against the newest version of glibc, it will always use t= he > newest symbols and that is by design. The problem is that this will just break GCC build in the future. Many peop= le are stuck with old versions of GCC and can't upgrade due to small issues li= ke this. Please fix it by avoid using arc4random in libstdc++ for glibc. thank= you=