unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
To: Dan Kegel <dank@kegel.com>
Cc: 29464@debbugs.gnu.org
Subject: bug#29464: gcc-7 breaks guile-2.2.2?
Date: Fri, 29 Dec 2017 13:11:52 -0600	[thread overview]
Message-ID: <87373t8i2v.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <87bmii839t.fsf@trouble.defaultvalue.org>

Rob Browning <rlb@defaultvalue.org> writes:

> I'm fairly sure it did, and a build with -fno-stack-protector just
> finished successfully, so for the moment, I think I may proceed with
> that and get the builds started on the other architectures.  Then I can
> try removing -O0 again.

OK, without -O0 and with -no-stack-protector, my local amd64 build was
fine, but ppc64el still crashes in test-out-of-memory:

  https://buildd.debian.org/status/package.php?p=guile-2.2&suite=sid

When I get a chance I'll try to poke around on a suitable porterbox.

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4





  reply	other threads:[~2017-12-29 19:11 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
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 [this message]
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=87373t8i2v.fsf@trouble.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --cc=29464@debbugs.gnu.org \
    --cc=dank@kegel.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.
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).