From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 24033@debbugs.gnu.org
Subject: bug#24033: Porting emacs-25 to GNU/Linux ppc64 with draft glibc 2.24
Date: Wed, 20 Jul 2016 17:59:27 +0300 [thread overview]
Message-ID: <83poq8z774.fsf@gnu.org> (raw)
In-Reply-To: <a1974a92-c3d8-f68e-9960-9543a95a4034@cs.ucla.edu> (message from Paul Eggert on Wed, 20 Jul 2016 10:02:32 +0200)
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Wed, 20 Jul 2016 10:02:32 +0200
>
> I'd like to backport the attached patch from master to emacs-25. The
> idea is that Emacs 25 should work with glibc 2.24 (which is still in
> draft form). glibc is withdrawing support for some deprecated symbols
> like malloc_set_state and __malloc_initialize_hook. Emacs is intended to
> be portable to systems lacking these symbols, but this apparently does
> not work on ppc64 and ppc64le platforms. As noted in
> <https://sourceware.org/ml/libc-alpha/2016-07/msg00546.html>, the
> attached patch has been tested on emacs-25 and works on the affected
> platforms. I've also tested it on unaffected platforms such as x86 and
> x86-64.
Would it be possible to tweak the patch so that it doesn't change the
code on platforms other than PPC64? Maybe I misunderstand, but it
looks like some changes are also being done in the non-PPC64 branches
of the patch, and I'd like to avoid that if possible. (It's okay to
move the code around and change it syntactically, as long as the
semantics is intact for non-PPC64 platforms.)
Thanks.
next prev parent reply other threads:[~2016-07-20 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 8:02 bug#24033: Porting emacs-25 to GNU/Linux ppc64 with draft glibc 2.24 Paul Eggert
2016-07-20 14:59 ` Eli Zaretskii [this message]
2016-07-20 17:09 ` Paul Eggert
2016-07-20 18:52 ` Eli Zaretskii
2016-07-21 11:30 ` 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=83poq8z774.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=24033@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
/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.