From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 5C53B385782F; Thu, 5 Nov 2020 04:44:35 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5C53B385782F From: "siddhesh at sourceware dot org" To: glibc-bugs@sourceware.org Subject: [Bug string/25399] undefined reference to `__warn_memset_zero_len' when changing gnuc version Date: Thu, 05 Nov 2020 04:44:35 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: string X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: siddhesh at sourceware dot org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: security- X-Bugzilla-Changed-Fields: cc resolution bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: glibc-bugs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Glibc-bugs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2020 04:44:35 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D25399 Siddhesh Poyarekar changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |siddhesh at sourceware dot= org Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #4 from Siddhesh Poyarekar --- This compilation issue has been fixed[1] upstream; clang and other non-gcc compilers should now be able to build the reproducer correctly without any linker errors. There is the outstanding issue where static libraries and objects built with older compilers against the older glibc may refuse to link correctly with current glibc. The __warn_memset_zero_len symbol has been missing for a wh= ile now and nobody has complained specifically about that yet, so it appears th= at this issue is rare and if not, being worked around in other ways. If one needs this to be fixed in glibc by providing __warn_memset_zero_len = and provide the linker warning, please file a new bug report to discuss it. [1] https://sourceware.org/pipermail/glibc-cvs/2020q4/070949.html --=20 You are receiving this mail because: You are on the CC list for the bug.=