From: Thomas Fitzsimmons <fitzsim@fitzsim.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 33174@debbugs.gnu.org
Subject: bug#33174: 27.0.50; Dump fails on GNU/Linux ppc64le
Date: Sun, 28 Oct 2018 08:56:59 -0400 [thread overview]
Message-ID: <CAEYera+4aC78gu5ykOCp-TOOxd8gyBgWy6jSFSKiraqudPf_9A@mail.gmail.com> (raw)
In-Reply-To: <b8d37c56-62e9-e6b7-85df-2847a980a495@cs.ucla.edu>
[-- Attachment #1: Type: text/plain, Size: 608 bytes --]
On 2018-10-28 4:05 AM, "Paul Eggert" <eggert@cs.ucla.edu> wrote:
>
> I built and ran Emacs master on two CentOS 7 ppc64le platforms with no
trouble. So the problem is not GNU/Linux ppc64le per se; it's something
more specific to your platform.
OK, thanks for checking. I'm running the Linux-libre 4.18 kernel built from
source with powernv_defconfig -- I should have mentioned that in the
initial report, sorry. I'll try the debugging steps you've suggested when
I get back to my system, and narrow down what the relevant options are.
Everything else on my system is stock Debian stretch packages.
Thomas
[-- Attachment #2: Type: text/html, Size: 755 bytes --]
next prev parent reply other threads:[~2018-10-28 12:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-27 10:35 bug#33174: 27.0.50; Dump fails on GNU/Linux ppc64le Thomas Fitzsimmons
2018-10-27 13:16 ` Thomas Fitzsimmons
2018-10-27 20:26 ` Paul Eggert
2018-10-28 8:05 ` Paul Eggert
2018-10-28 12:56 ` Thomas Fitzsimmons [this message]
2018-10-28 19:22 ` Paul Eggert
2018-10-30 1:28 ` Thomas Fitzsimmons
2018-10-30 2:16 ` Paul Eggert
2018-10-29 1:47 ` Thomas Fitzsimmons
2018-10-29 7:22 ` Paul Eggert
2018-10-30 2:44 ` Thomas Fitzsimmons
2018-10-30 5:58 ` Paul Eggert
2018-10-30 9:30 ` Thomas Fitzsimmons
2018-11-12 6:39 ` Paul Eggert
2018-11-12 17:24 ` Andy Moreton
2018-11-13 2:29 ` Thomas Fitzsimmons
2018-11-13 14:42 ` Paul Eggert
2018-11-19 3:14 ` Thomas Fitzsimmons
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAEYera+4aC78gu5ykOCp-TOOxd8gyBgWy6jSFSKiraqudPf_9A@mail.gmail.com \
--to=fitzsim@fitzsim.org \
--cc=33174@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).