unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Ed Green <eug2@psu.edu>
To: 17399@debbugs.gnu.org
Subject: bug#17399: compilation bugs when making guile-2.0.11
Date: Sat, 03 May 2014 19:50:21 -0400	[thread overview]
Message-ID: <536580BD.5030205@psu.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 916 bytes --]

Dear GNU guile team:

I compiled guile-2.0.11 yesterday, using the configure file in the
distribution and the resulting makefile.

I would like to report three things. Output of ./configure requested
that I report the second one.

I was able to compile and install guile. To the extent that I have
tested it, it works fine. (Thanks!)

Here are the problems. The attached .pdf file will walk you through them
in detail, starting with describing my system. I would be happy to
provide further information or output from the installation process, if
you would like to have it.

1. readline 6.2 is installed. The configure program identified it as
something prior to version 2.1, and output a warning.

2. Running "make check" produced an error report from "ports test:
unicode byte-order marks".

3. The make process produced a file, unistr.h, that had to be manually
adjusted in order to compile.

Sincerely,
Ed Green

[-- Attachment #2: bug-guile-20140502.pdf --]
[-- Type: application/pdf, Size: 52152 bytes --]

             reply	other threads:[~2014-05-03 23:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-03 23:50 Ed Green [this message]
2014-05-28 17:35 ` bug#17399: compilation bugs when making guile-2.0.11 Ludovic Courtès

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=536580BD.5030205@psu.edu \
    --to=eug2@psu.edu \
    --cc=17399@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).