From: Matt Wette <matt.wette@gmail.com>
To: guile-devel@gnu.org
Subject: Re: GNU Guile 2.9.6 Released [beta]
Date: Sat, 7 Dec 2019 08:05:15 -0800 [thread overview]
Message-ID: <693ae476-6225-4e97-4f4b-a2e3a00a6b20@gmail.com> (raw)
In-Reply-To: <87wob9wq7x.fsf@pobox.com>
On 12/6/19 5:14 AM, Andy Wingo wrote:
> We are pleased to announce GNU Guile release 2.9.6. This is the sixth
> pre-release of what will eventually become the 3.0 release series.
>
>
Same error I get w/ 2.9.5, on Ubuntu 18.04:
BOOTSTRAP GUILEC system/vm/linker.go
/bin/bash: line 6: 9159 Segmentation fault (core dumped)
GUILE_AUTO_COMPILE=0 ../meta/build-env guild compile
--target="x86_64-pc-linux-gnu" -O1 -Oresolve-primitives -L
"/home/mwette/proj/guile/guile-2.9.6/module" -L
"/home/mwette/proj/guile/guile-2.9.6/guile-readline" -o
"system/vm/linker.go" "../module/system/vm/linker.scm"
Makefile:1930: recipe for target 'system/vm/linker.go' failed
make[2]: *** [system/vm/linker.go] Error 139
I tried to get the guild-compile running under
meta/gdb-uninstalled-guile but failed.
Matt
prev parent reply other threads:[~2019-12-07 16:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 13:14 GNU Guile 2.9.6 Released [beta] Andy Wingo
2019-12-07 0:44 ` Brett Gilio
2019-12-07 16:05 ` Matt Wette [this message]
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=693ae476-6225-4e97-4f4b-a2e3a00a6b20@gmail.com \
--to=matt.wette@gmail.com \
--cc=guile-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.
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).