From: Paul Eggert <eggert@cs.ucla.edu>
To: "Florian Weimer" <fweimer@redhat.com>,
"Jan Synáček" <jsynacek@redhat.com>
Cc: 23760@debbugs.gnu.org
Subject: bug#23760: 25.0.95; emacs 25.0.95 doesn't build with glibc-2.23.90
Date: Mon, 20 Jun 2016 12:04:50 +0200 [thread overview]
Message-ID: <5767BFC2.3090504@cs.ucla.edu> (raw)
In-Reply-To: <10c68790-0574-d3bd-752f-f5562ebf9fcb@redhat.com>
On 06/20/2016 11:21 AM, Florian Weimer wrote:
>
> The usual mechanism for deprecation and removal of an API does not
> work if the symbol is interposed because it will be unversioned, and
> unversioned symbols preempt versioned symbols. As a result, even if
> the symbol is a compat symbol, you can produce new binaries which use
> the removed API.
>
True, but in this particular case Emacs is replacing malloc as well as
__malloc_initialize_hook etc., so I don't see a problem. Although new
Emacs binaries will still use the removed API, they will also support
the removed API.
What *could* be a problem is if the new glibc malloc API supplies
symbols that Emacs does not supply, and if other parts of the new glibc
use these symbols. But I don't see this happening either (and if it did
happen, poisoning __malloc_initialize_hook wouldn't fix it).
Perhaps poisoning __malloc_initialize_hook helps for some theoretical
applications, but for Emacs I don't see how it is a win.
next prev parent reply other threads:[~2016-06-20 10:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 10:48 bug#23760: 25.0.95; emacs 25.0.95 doesn't build with glibc-2.23.90 Jan Synáček
2016-06-13 15:58 ` Glenn Morris
2016-06-14 6:09 ` Jan Synacek
2016-06-14 6:17 ` Florian Weimer
2016-06-19 3:02 ` Paul Eggert
2016-06-20 8:48 ` Florian Weimer
2016-06-20 9:03 ` Paul Eggert
2016-06-20 9:21 ` Florian Weimer
2016-06-20 10:04 ` Paul Eggert [this message]
2016-06-20 10:15 ` Florian Weimer
2016-07-06 13:29 ` Paul Eggert
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=5767BFC2.3090504@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=23760@debbugs.gnu.org \
--cc=fweimer@redhat.com \
--cc=jsynacek@redhat.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.