unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Dan Kegel <dank@kegel.com>
To: 29464@debbugs.gnu.org
Subject: bug#29464: gcc-7 breaks guile-2.2.2?
Date: Mon, 27 Nov 2017 08:42:19 -0800	[thread overview]
Message-ID: <CAPF-yOYb7sJJ=X4z6md+jejXCLA7575E8Qd0KA61P-4pOXVkYg@mail.gmail.com> (raw)
In-Reply-To: <CAPF-yObbCn4dOd626aAmKuugnxc2LadQk6gPydA3RQPW_LNd=g@mail.gmail.com>

Update from http://lists.gnu.org/archive/html/guile-user/2017-11/msg00066.html :

---snip---
With gcc-7.2.0 and gcc-6.4.0, both built from source (just guile/configure ...
CC=gcc-X.X).

- stable-2.2 with 6.4 passes the tests every time.

- stable 2.2 with 7.2 fails on test-out-of-memory. Running make check
repeatedly I got F F F P F  F P P P P  F F F F P.
---snip---





  reply	other threads:[~2017-11-27 16:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-27  4:17 bug#29464: gcc-7 breaks guile-2.2.2? Dan Kegel
2017-11-27 16:42 ` Dan Kegel [this message]
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-yOYb7sJJ=X4z6md+jejXCLA7575E8Qd0KA61P-4pOXVkYg@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).