all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Jan Synacek <jsynacek@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: Tue, 14 Jun 2016 08:17:22 +0200	[thread overview]
Message-ID: <21855d8d-3725-aa8e-2243-6b3d7765c35f@redhat.com> (raw)
In-Reply-To: <CAPsXM8X3Rxq3bRStGGqDRqyqsYfs5CxQ36JVjiyJ5koYr-z9Yw@mail.gmail.com>

On 06/14/2016 08:09 AM, Jan Synacek wrote:
> On Mon, Jun 13, 2016 at 5:58 PM, Glenn Morris <rgm@gnu.org> wrote:
>> Jan Synáček wrote:
>>
>>> Emacs doesn't build with the latest glibc (glibc-2.23-90):
>>>
>>>   CC       gmalloc.o
>>> ../../src/gmalloc.c:273:15: error: attempt to use poisoned "__malloc_initialize_hook"
>>
>> I guess this might be fixed already?
>>
>> https://sourceware.org/ml/libc-alpha/2016-06/msg00500.html
>> "Revert symbol poisoning of  __malloc_initialize_hook."
>
> It was my understanding that this needed to be fixed in both glibc and Emacs.

Correct, Emacs should not use symbols in the implementation namespace.

Names such as __malloc_initialize_hook (with two leading underscores) 
could be reserved by other implementations as well, not just glibc.

Thanks,
Florian





  reply	other threads:[~2016-06-14  6:17 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 [this message]
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
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=21855d8d-3725-aa8e-2243-6b3d7765c35f@redhat.com \
    --to=fweimer@redhat.com \
    --cc=23760@debbugs.gnu.org \
    --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.