From: Paul Eggert <eggert@cs.ucla.edu>
To: Robert Pluim <rpluim@gmail.com>
Cc: Greg Minshall <minshall@acm.org>, emacs-devel@gnu.org
Subject: Re: make check fails? (emacs-26.1 w/modules)
Date: Wed, 12 Sep 2018 07:56:05 -0700 [thread overview]
Message-ID: <c5601a8e-d9d3-c470-c9e8-001a9398448a@cs.ucla.edu> (raw)
In-Reply-To: <87sh2e96jg.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 118 bytes --]
Thanks for tracking this down. It's worth a note in etc/PROBLEMS; I installed
the attached into the emacs-26 branch.
[-- Attachment #2: 0001-etc-PROBLEMS-Document-Ubuntu-16.04-issue.patch --]
[-- Type: text/x-patch, Size: 1021 bytes --]
From 41cdda22c78eb0b00612ce25cdb356dd64322fcc Mon Sep 17 00:00:00 2001
From: Paul Eggert <eggert@cs.ucla.edu>
Date: Wed, 12 Sep 2018 07:53:43 -0700
Subject: [PATCH] * etc/PROBLEMS: Document Ubuntu 16.04 issue.
---
etc/PROBLEMS | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/etc/PROBLEMS b/etc/PROBLEMS
index 15e2b3359d..7dfafe04de 100644
--- a/etc/PROBLEMS
+++ b/etc/PROBLEMS
@@ -2986,6 +2986,15 @@ as a macro. If the definition (in both unex*.c and malloc.c) is wrong,
it can cause problems like this. You might be able to find the correct
value in the man page for a.out(5).
+* 'make check' failures
+
+** emacs-module-tests fail on Ubuntu 16.04
+
+This is due to a bug in GCC that was fixed in 2015; see
+<https://lists.gnu.org/r/emacs-devel/2018-09/msg00548.html>.
+You can work around the problem by using a later version of GCC or of
+Ubuntu, or by configuring without modules.
+
* Problems on legacy systems
This section covers bugs reported on very old hardware or software.
--
2.17.1
next prev parent reply other threads:[~2018-09-12 14:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-03 14:39 make check fails? (emacs-26.1 w/modules) Greg Minshall
2018-09-03 15:12 ` Greg Minshall
2018-09-03 15:13 ` Eli Zaretskii
2018-09-03 15:16 ` Greg Minshall
2018-09-03 15:18 ` Greg Minshall
2018-09-04 10:39 ` Greg Minshall
2018-09-05 7:54 ` Paul Eggert
2018-09-05 9:14 ` Greg Minshall
2018-09-05 20:26 ` Greg Minshall
2018-09-05 20:55 ` Paul Eggert
2018-09-06 8:58 ` Robert Pluim
2018-09-06 10:32 ` Greg Minshall
2018-09-12 13:41 ` Robert Pluim
2018-09-12 14:56 ` Paul Eggert [this message]
2018-09-12 16:19 ` Greg Minshall
2018-09-12 16:37 ` Robert Pluim
2018-09-12 16:27 ` Greg Minshall
2018-09-12 16:39 ` Robert Pluim
2018-09-07 9:10 ` Greg Minshall
2018-09-03 18:27 ` Paul Eggert
2018-09-03 23:46 ` Greg Minshall
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=c5601a8e-d9d3-c470-c9e8-001a9398448a@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=minshall@acm.org \
--cc=rpluim@gmail.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 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).