unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: saffronsnail@hushmail.com
To: 25509@debbugs.gnu.org
Subject: bug#25509: Guile 2.1.6 build fails on FreeBSD 11.0
Date: Sun, 22 Jan 2017 18:02:11 -0800	[thread overview]
Message-ID: <20170123020212.53B20404D9@smtp.hushmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 376 bytes --]

Hello, 
I saw the email about the 2.1.6 testing release. I previously
submitted a bug report about Guile 2.0.13 failing, but this build is
giving me different errors so I wanted to submit this as well. I ran
the following commands:
autoconfautomake./configuremake
I have attached text files containing the output of the commands, when
they produced output.
Thanks,saffronsnail

[-- Attachment #1.2: Type: text/html, Size: 579 bytes --]

[-- Attachment #2: output.tar.gz --]
[-- Type: application/x-gzip, Size: 10975 bytes --]

             reply	other threads:[~2017-01-23  2:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-23  2:02 saffronsnail [this message]
2017-03-16  3:11 ` bug#25509: FreeBSD 11.0 Matt Wette
2017-04-19 15:24   ` 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=20170123020212.53B20404D9@smtp.hushmail.com \
    --to=saffronsnail@hushmail.com \
    --cc=25509@debbugs.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).