From: Dan Kegel <dank@kegel.com>
To: 29464@debbugs.gnu.org
Subject: bug#29464: gcc-7 breaks guile-2.2.2?
Date: Sun, 26 Nov 2017 20:17:59 -0800 [thread overview]
Message-ID: <CAPF-yObbCn4dOd626aAmKuugnxc2LadQk6gPydA3RQPW_LNd=g@mail.gmail.com> (raw)
Building guile-2.2.2 seems fine on Ubuntu 17.04, but fails with
Warning: Unwind-only `out-of-memory' exception; skipping pre-unwind handler.
FAIL: test-out-of-memory
==================================
1 of 39 tests failed
Please report to bug-guile@gnu.org
on Ubuntu 17.10. libgc is the same version on both, but gcc is different...
and if I pick gcc-6 on ubuntu 17.10 (instead of the default gcc-7),
it seems to succeed.
Mentioned at
https://bugs.launchpad.net/ubuntu/+source/guile-2.2/+bug/1734575
https://lists.gnu.org/archive/html/guile-user/2017-11/msg00062.html
Possibly related to
https://lists.gnu.org/archive/html/help-guix/2017-11/msg00016.html
next reply other threads:[~2017-11-27 4:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 4:17 Dan Kegel [this message]
2017-11-27 16:42 ` bug#29464: gcc-7 breaks guile-2.2.2? Dan Kegel
2017-12-29 0:09 ` Rob Browning
2017-12-29 0:53 ` Dan Kegel
2017-12-29 6:19 ` Rob Browning
2017-12-29 19:11 ` Rob Browning
2017-12-29 19:27 ` Rob Browning
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPF-yObbCn4dOd626aAmKuugnxc2LadQk6gPydA3RQPW_LNd=g@mail.gmail.com' \
--to=dank@kegel.com \
--cc=29464@debbugs.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.
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).