From: Andy Wingo <wingo@pobox.com>
To: saffronsnail@hushmail.com
Cc: 25324@debbugs.gnu.org
Subject: bug#25324: Make check fails on FreeBSD 11.0
Date: Mon, 09 Jan 2017 22:57:18 +0100 [thread overview]
Message-ID: <878tqjaoch.fsf@pobox.com> (raw)
In-Reply-To: <20170101194728.BA412C0674@smtp.hushmail.com> (saffronsnail@hushmail.com's message of "Sun, 01 Jan 2017 11:47:28 -0800")
On Sun 01 Jan 2017 20:47, saffronsnail@hushmail.com writes:
> FreeBSD packages Guile 1.8 so I am performing a source build of Guile
> 2.0.9. I was able to configure it to get guile to compile, but the
> following tests fail when I run make check:
Any reason to avoid 2.0.13 ? It's newer and probably fixes a number of
compilation bugs.
Andy
next prev parent reply other threads:[~2017-01-09 21:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-01 19:47 bug#25324: Make check fails on FreeBSD 11.0 saffronsnail
2017-01-09 21:57 ` Andy Wingo [this message]
2017-05-18 3:40 ` 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=878tqjaoch.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=25324@debbugs.gnu.org \
--cc=saffronsnail@hushmail.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).