From: <dsmich@roadrunner.com>
To: guile-devel@gnu.org, dsmich@roadrunner.com, Andy Wingo <wingo@pobox.com>
Subject: Re: guile 3 update, june 2018 edition
Date: Tue, 17 Jul 2018 6:32:27 -0400 [thread overview]
Message-ID: <20180717103227.2A6TF.164673.root@cdptpa-web09> (raw)
In-Reply-To: <20180702040239.BD1LI.118872.root@cdptpa-web09>
---- dsmich@roadrunner.com wrote:
> Ok! now getting past the "make -j" issue, but I'm still getting a segfault.
And now commit e6461cf1b2b63e3ec9a2867731742db552b61b71 has gotten past the segfault.
Wooo!
-Dale
next prev parent reply other threads:[~2018-07-17 10:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 8:13 guile 3 update, june 2018 edition Andy Wingo
2018-06-30 0:40 ` dsmich
2018-07-02 4:02 ` dsmich
2018-07-17 10:32 ` dsmich [this message]
2018-07-02 9:28 ` Ludovic Courtès
2018-07-05 17:05 ` Andy Wingo
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=20180717103227.2A6TF.164673.root@cdptpa-web09 \
--to=dsmich@roadrunner.com \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.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).