From: Matt Wette <matt.wette@gmail.com>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: GNU Guile 2.2.2 released
Date: Sat, 13 May 2017 06:05:32 -0700 [thread overview]
Message-ID: <947EA843-A72C-4669-A024-7DB8C0FE252A@gmail.com> (raw)
In-Reply-To: <878tmt4yd3.fsf@pobox.com>
> On Apr 21, 2017, at 7:41 AM, Andy Wingo <wingo@pobox.com> wrote:
>
> We sheepishly announce GNU Guile release 2.2.2, a quick bug-fix to the
> recent 2.2.1 release.
The FreeBSD section in README is not quite correct IMO. Here are suggested changes:
FreeBSD 11.0:
- For a build supporting threads, please `pkg install' the following
+ Please `pkg install' the following:
- pkgconf : provides pkg-config
+ - texinfo : provides makeinfo
- gmake : /usr/bin/make does not work
- - boehm-gc-threaded : needed for threaded support
- Configure as:
+ If you want a Guile with threads, then install boehm-gc-threaded and
+ configure as:
./configure --with-bdw-gc=bdw-gc-threaded
next prev parent reply other threads:[~2017-05-13 13:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 14:41 GNU Guile 2.2.2 released Andy Wingo
2017-05-13 13:05 ` Matt Wette [this message]
2017-05-15 20:09 ` Andy Wingo
2017-05-16 11:43 ` ff
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=947EA843-A72C-4669-A024-7DB8C0FE252A@gmail.com \
--to=matt.wette@gmail.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).