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 11:03:02 +0200 [thread overview]
Message-ID: <5767B146.30902@cs.ucla.edu> (raw)
In-Reply-To: <c9299dba-886e-9edd-c7b1-3340cfadbece@redhat.com>
On 06/20/2016 10:48 AM, Florian Weimer wrote:
>> aren't we better off having glibc simply not declare
>> __malloc_initialize_hook?
>
> You mean, not declare it in <malloc.h>?
Yes, that's what I meant.
>
> I'm more worried about the other __ variables in the Emacs malloc.
> Their in Emacs definition does not even match the one in glibc. The
> difference is probably harmless, but it is fairly close to be being
> broken.
The intent is that __malloc_initialize_hook and the other __ variables
will become inoperative in glibc, right? That is, glibc won't set or use
or care about these obsolete variables. If so, we should be OK with
Emacs master as-is: when it substitutes its own (even-more-obsolescent)
malloc it will set and use these variables freely, and this won't
collide with any glibc use.
next prev parent reply other threads:[~2016-06-20 9:03 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 [this message]
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=5767B146.30902@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.