From: Mark H Weaver <mhw@netris.org>
To: Hans Aberg <haberg-1@telia.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, 19237-done@debbugs.gnu.org
Subject: bug#19237: Guile-2.0.11 OS X 10.10.1 build error
Date: Thu, 04 Dec 2014 18:47:43 -0500 [thread overview]
Message-ID: <87388v6kps.fsf@yeeloong.lan> (raw)
In-Reply-To: <13044C92-0817-4F77-AE56-CA40B55C2B20@telia.com> (Hans Aberg's message of "Thu, 4 Dec 2014 20:28:15 +0100")
Hans Aberg <haberg-1@telia.com> writes:
>> 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.
Can you explain this more clearly? What do you think Guile expects to
be in one file that "readline now has in several"? Also, how did you
reach this conclusion, given that GNU Readline apparently wasn't
installed when the build failed?
FWIW, we regularly build the latest Guile with the latest Readline in
GNU Guix, and haven't run into this problem.
Regards,
Mark
next prev parent reply other threads:[~2014-12-04 23:47 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
2014-12-04 23:47 ` Mark H Weaver [this message]
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=87388v6kps.fsf@yeeloong.lan \
--to=mhw@netris.org \
--cc=19237-done@debbugs.gnu.org \
--cc=haberg-1@telia.com \
--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).