From: Hans Aberg <haberg@math.su.se>
To: Neil Jerram <neil@ossau.uklinux.net>
Cc: bug-guile@gnu.org
Subject: Re: Guile-1.8.4 compile bug Mac OS X 10.4.11 PPC G4
Date: Fri, 7 Mar 2008 22:20:28 +0100 [thread overview]
Message-ID: <829CC0A2-DAC2-416C-8598-E118F1884064@math.su.se> (raw)
In-Reply-To: <87pru6cnqy.fsf@ossau.uklinux.net>
On 7 Mar 2008, at 20:55, Neil Jerram wrote:
> From our new FAQ (which will be part of the distribution in 1.8.5):
>
> ========FAQ=========
> ** readline.c: error: `rl_pending_input' undeclared
>
> This occurs if the Readline library detected by Guile's configure
> script is actually the BSD Editline project's supposedly
> Readline-compatible library. The immediate fix is to uninstall
> Editline and install the real GNU Readline instead. When you do this,
> please note that it probably won't work to keep Editline in /usr and
> install GNU Readline in /usr/local (or some similar arrangement),
> because the Editline library will then still be picked up at link and
> run time; it's best (subject to other constraints) to remove Editline
> completely.
>
> For the longer term, please also report this problem to the Editline
> project, to encourage them to fix it in the next release of their
> Readline compatibility library.
> ========FAQ=========
>
> Does that help?
This might indeed be the problem - I think I saw that Mac OS X comes
with Editline.
I have since installed Readline; I need to check if it fixes it.
Otherwise, a fix might be that the Guile installation checks for
readline in /usr/local/.
Hans Aberg
next prev parent reply other threads:[~2008-03-07 21:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 18:03 Guile-1.8.4 compile bug Mac OS X 10.4.11 PPC G4 Hans Aberg
2008-02-23 10:13 ` Ludovic Courtès
2008-02-23 18:21 ` Neil Jerram
2008-03-07 19:55 ` Neil Jerram
2008-03-07 21:20 ` Hans Aberg [this message]
2008-03-07 22:21 ` Neil Jerram
2008-03-07 23:13 ` Hans Aberg
2008-03-08 12:19 ` Neil Jerram
2008-03-08 13:48 ` 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=829CC0A2-DAC2-416C-8598-E118F1884064@math.su.se \
--to=haberg@math.su.se \
--cc=bug-guile@gnu.org \
--cc=neil@ossau.uklinux.net \
/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).