public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug string/25399] undefined reference to `__warn_memset_zero_len' when changing gnuc version
       [not found] <bug-25399-131@http.sourceware.org/bugzilla/>
@ 2020-11-05  4:44 ` siddhesh at sourceware dot org
  2020-11-05 16:12 ` fweimer at redhat dot com
  2021-08-25 16:36 ` ovilewade9 at gmail dot com
  2 siblings, 0 replies; 3+ messages in thread
From: siddhesh at sourceware dot org @ 2020-11-05  4:44 UTC (permalink / raw)
  To: glibc-bugs

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.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug string/25399] undefined reference to `__warn_memset_zero_len' when changing gnuc version
       [not found] <bug-25399-131@http.sourceware.org/bugzilla/>
  2020-11-05  4:44 ` [Bug string/25399] undefined reference to `__warn_memset_zero_len' when changing gnuc version siddhesh at sourceware dot org
@ 2020-11-05 16:12 ` fweimer at redhat dot com
  2021-08-25 16:36 ` ovilewade9 at gmail dot com
  2 siblings, 0 replies; 3+ messages in thread
From: fweimer at redhat dot com @ 2020-11-05 16:12 UTC (permalink / raw)
  To: glibc-bugs

https://sourceware.org/bugzilla/show_bug.cgi?id=25399

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |2.33

--- Comment #5 from Florian Weimer <fweimer at redhat dot com> ---
Fixed by:

commit dc274b141666766b8ef70992d887e3c0c5e41bed
Author: Siddhesh Poyarekar <siddhesh@sourceware.org>
Date:   Tue Nov 3 15:09:28 2020 +0530

    Remove __warn_memset_zero_len [BZ #25399]

    Non-gcc compilers (clang and possibly other compilers that do not
    masquerade as gcc 5.0 or later) are unable to use
    __warn_memset_zero_len since the symbol is no longer available on
    glibc built with gcc 5.0 or later.  While it was likely an oversight
    that caused this omission, the fact that it wasn't noticed until
    recently (when clang closed the gap on _FORTIFY_SUPPORT) that the
    symbol was missing.

    Given that both gcc and clang are capable of doing this check in the
    compiler, drop all remaining signs of __warn_memset_zero_len from
    glibc so that no more objects are built with this symbol in future.

We should consider backports.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug string/25399] undefined reference to `__warn_memset_zero_len' when changing gnuc version
       [not found] <bug-25399-131@http.sourceware.org/bugzilla/>
  2020-11-05  4:44 ` [Bug string/25399] undefined reference to `__warn_memset_zero_len' when changing gnuc version siddhesh at sourceware dot org
  2020-11-05 16:12 ` fweimer at redhat dot com
@ 2021-08-25 16:36 ` ovilewade9 at gmail dot com
  2 siblings, 0 replies; 3+ messages in thread
From: ovilewade9 at gmail dot com @ 2021-08-25 16:36 UTC (permalink / raw)
  To: glibc-bugs

https://sourceware.org/bugzilla/show_bug.cgi?id=25399

ovile009988 <ovilewade9 at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ovilewade9 at gmail dot com

--- Comment #6 from ovile009988 <ovilewade9 at gmail dot com> ---
I am exited to all time this game follow https://freevbucksblog.com and see
free vbucks codes online game all time.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2021-08-25 16:36 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <bug-25399-131@http.sourceware.org/bugzilla/>
2020-11-05  4:44 ` [Bug string/25399] undefined reference to `__warn_memset_zero_len' when changing gnuc version siddhesh at sourceware dot org
2020-11-05 16:12 ` fweimer at redhat dot com
2021-08-25 16:36 ` ovilewade9 at gmail dot com

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).