|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|
|User-agent:||Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.8.0|
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.
|[Prev in Thread]||Current Thread||[Next in Thread]|