From: Andy Wingo <wingo@igalia.com>
To: Matt Wette <matt.wette@gmail.com>
Cc: 26183-done@debbugs.gnu.org
Subject: bug#26183: patch for guile-2.2.0 on FreeBSD 11.0
Date: Wed, 19 Apr 2017 16:20:37 +0200 [thread overview]
Message-ID: <87pog8mqbu.fsf@igalia.com> (raw)
In-Reply-To: <8B56029B-58C3-44B1-838E-3F2BB84255C8@gmail.com> (Matt Wette's message of "Sun, 19 Mar 2017 18:39:46 -0700")
On Mon 20 Mar 2017 02:39, Matt Wette <matt.wette@gmail.com> writes:
> Attached is a patch to apply to guile-2.2.0 to compile on FreeBSD 11.0
> Changes
> 1) updated README to indicate which extra FreeBSD packages need to be installed
> 2) minor change to configure.ac (implies autoconf needs to run) to use bdw-gc-threaded instead of bdw-gc
> With this, I had successful configure, gmake, and gmake check.
Applied with some adaptations. Please see git master and test. Thanks!
Andy
next prev parent reply other threads:[~2017-04-19 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 1:39 bug#26183: patch for guile-2.2.0 on FreeBSD 11.0 Matt Wette
2017-04-19 14:20 ` Andy Wingo [this message]
2017-04-25 13:04 ` Matt Wette
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=87pog8mqbu.fsf@igalia.com \
--to=wingo@igalia.com \
--cc=26183-done@debbugs.gnu.org \
--cc=matt.wette@gmail.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).