From: Barry Warsaw <barry@python.org>
To: emacs-devel@gnu.org
Subject: Emacs 25.1 build failures on Ubuntu arm64
Date: Tue, 28 Mar 2017 20:30:40 -0400 [thread overview]
Message-ID: <20170328203040.0a1e0b98@subdivisions.wooz.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2112 bytes --]
I'm not sure how much of this email will be actionable, but I wanted to at
least let y'all know about a problem we've seen building Emacs 25.1 on Ubuntu
17.04 arm64.
Quick background: In Ubuntu we have a few minor changes above the package in
Debian, which we mostly inherit. One of those changes is that we build with
-j1 on arm64 only. There are a couple of other changes that shouldn't have an
impact on the problem I'll describe, but the changelogs can be easily
inspected.
In any case, for several weeks now we've seen Emacs segfault on arm64 builders
consistently in what I think are the CEDET tests. The full traceback, when
we've been able to capture it, is here:
https://launchpadlibrarian.net/302409391/gdb-bt-full.txt
The full build log is here:
https://launchpadlibrarian.net/310046964/buildlog_ubuntu-zesty-arm64.emacs25_25.1+1-3ubuntu3~ppa0_BUILDING.txt.gz
(scroll to the bottom to see the crash)
and the bug that tracks this is here:
https://bugs.launchpad.net/ubuntu/+source/emacs25/+bug/1656474
We're using gcc based on 6.2.1/6.3.0 (depending on the build).
All the other architectures have been building fine, but arm64 crashes
consistently on our build machines. Attempts to reproduce the crash on
development machines, even on arm64 chroots and bare metal have not been
successful, so debugging the problem isn't easy. Based on some research into
other crashes, various other attempts to work around the problem, and some
discussions among Ubuntu developers on IRC, we wondered whether turning off
optimization would help. Indeed, adding -O0 to CFLAGS only on arm64 solved
the problem in a test build.
I've now uploaded a new build to the archive with -O0 on arm64 and I expect
this to build and get published once it's approved (Ubuntu is currently in
final beta freeze).
I'll watch this thread via Gmane and try to answer any additional questions
you might have. As I said, I'm not sure what the Emacs developers can do
about it, but I wanted you to know about the problem and how we think we've
solved it.
Cheers,
-Barry
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next reply other threads:[~2017-03-29 0:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 0:30 Barry Warsaw [this message]
2017-03-29 15:03 ` Emacs 25.1 build failures on Ubuntu arm64 Eli Zaretskii
2017-03-29 20:46 ` Barry Warsaw
2017-03-29 21:57 ` Barry Warsaw
2017-08-01 14:55 ` Rob Browning
2017-08-04 12:26 ` Byung-Hee HWANG (황병희, 黃炳熙)
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=20170328203040.0a1e0b98@subdivisions.wooz.org \
--to=barry@python.org \
--cc=emacs-devel@gnu.org \
/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.