unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Hans Aberg <haberg-1@telia.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 19237-done@debbugs.gnu.org
Subject: bug#19237: Guile-2.0.11 OS X 10.10.1 build error
Date: Thu, 4 Dec 2014 20:28:15 +0100	[thread overview]
Message-ID: <13044C92-0817-4F77-AE56-CA40B55C2B20@telia.com> (raw)
In-Reply-To: <87r3wf1g87.fsf@gnu.org>


> On 4 Dec 2014, at 18:23, Ludovic Courtès <ludo@gnu.org> wrote:
> 
> Hans Aberg <haberg-1@telia.com> skribis:
> 
>>> On 3 Dec 2014, at 23:21, Ludovic Courtès <ludo@gnu.org> wrote:
>>> 
>>> Could it be because Guile is being compiled against libeditline instead
>>> of GNU Readline?
>>> 
>>> Readline support in Guile requires GNU Readline.
>> 
>> It looked as though that the readline in the Guile distribution is too
>> old - no other readline installed on the system.
> 
> Actually there’s no Readline in Guile itself, just the guile-readline
> bindings.

I think the binding problem was that what Guile expected to be in one file, readline now has in several.

>> I just installed the latest GNU readline into /usr/local/, and then
>> Guile compiled.
> 
> OK, so I guess it was really libeditline’s Readline semi-compatibility
> shim that was being used.

Yes, there was some compatibility file, with the problem as above.

> Closing this bug now.

OK.







  reply	other threads:[~2014-12-04 19:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-30 23:51 bug#19237: Guile-2.0.11 OS X 10.10.1 build error Hans Aberg
2014-12-03 22:21 ` Ludovic Courtès
2014-12-03 22:32   ` Hans Aberg
2014-12-04 17:23     ` Ludovic Courtès
2014-12-04 19:28       ` Hans Aberg [this message]
2014-12-04 23:47         ` Mark H Weaver
2014-12-05  9:28           ` Hans Aberg

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=13044C92-0817-4F77-AE56-CA40B55C2B20@telia.com \
    --to=haberg-1@telia.com \
    --cc=19237-done@debbugs.gnu.org \
    --cc=ludo@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).