public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "siddhesh at sourceware dot org" <sourceware-bugzilla@sourceware.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 [thread overview]
Message-ID: <bug-25399-131-yoppm33Awf@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25399-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25399
Siddhesh Poyarekar <siddhesh at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |siddhesh at sourceware dot org
Resolution|--- |FIXED
Status|NEW |RESOLVED
--- Comment #4 from Siddhesh Poyarekar <siddhesh at sourceware dot org> ---
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 while
now and nobody has complained specifically about that yet, so it appears that
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
--
You are receiving this mail because:
You are on the CC list for the bug.
next parent reply other threads:[~2020-11-05 4:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-25399-131@http.sourceware.org/bugzilla/>
2020-11-05 4:44 ` siddhesh at sourceware dot org [this message]
2020-11-05 16:12 ` fweimer at redhat dot com
2021-08-25 16:36 ` ovilewade9 at gmail dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-25399-131-yoppm33Awf@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).