From: Paul Eggert <eggert@cs.ucla.edu>
To: "Jan Synáček" <jsynacek@redhat.com>
Cc: Florian Weimer <fweimer@redhat.com>, 23760@debbugs.gnu.org
Subject: bug#23760: 25.0.95; emacs 25.0.95 doesn't build with glibc-2.23.90
Date: Sun, 19 Jun 2016 05:02:17 +0200 [thread overview]
Message-ID: <57660B39.5080909@cs.ucla.edu> (raw)
In-Reply-To: <m6flh29bbzs.fsf@jsynacek-ntb.brq.redhat.com>
If I understand things correctly, the Emacs 'configure' script
discovered that the test glibc version did not declare and define a
symbol __malloc_initialize_hook, and so Emacs supplied its own
implementation of malloc, complete with __malloc_initialize_hook. Since
__malloc_initialize_hook was poisoned, this didn't work.
I suppose Emacs could work around the problem by using
__malloc_initialize_hook when linked against an old glibc, and by using
a new symbol emacs_malloc_initialize_hook when linked against its
substitute implementation. Although this would insulate distant-future
versions of Emacs against the poisoning, it wouldn't work for Emacs 25
(the next Emacs version) and earlier; these systems would be unbuildable
with a glibc that poisons __malloc_initialize_hook. So as a practical
matter, aren't we better off having glibc simply not declare
__malloc_initialize_hook? That should work with older Emacs versions,
which is a win. I don't see a significant practical advantage to
poisoning the symbol.
next prev parent reply other threads:[~2016-06-19 3:02 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 [this message]
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
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=57660B39.5080909@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.