unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: "Neil Jerram" <neiljerram@googlemail.com>
To: "Frank J. R. Hanstick" <trog24@comcast.net>
Cc: guile-user@gnu.org
Subject: Re: Compilation failure.
Date: Wed, 28 May 2008 14:59:30 +0100	[thread overview]
Message-ID: <49dd78620805280659x37405d88l4e67ec7ba56a0934@mail.gmail.com> (raw)
In-Reply-To: <FCF69BAB-750F-4171-A556-7346C2E37192@comcast.net>

2008/5/28 Frank J. R. Hanstick <trog24@comcast.net>:
> Hello,
>        I am trying to build guile for MacOS 10.4.11 and run into the
> following error:
>
> readline.c:109: error: 'rl_pending_input' undeclared (first use in this
> function)

Please see the "FAQ" file, which reads as appended below.  In case
that doesn't help, please let us know.

Regards,
         Neil


** 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.




  reply	other threads:[~2008-05-28 13:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-28 12:53 Compilation failure Frank J. R. Hanstick
2008-05-28 13:59 ` Neil Jerram [this message]
     [not found]   ` <92338D2C-2E45-43A4-B4A7-AF5CAD54BF38@comcast.net>
2009-06-29 20:55     ` Neil Jerram
     [not found]       ` <87prcmpwtt.fsf@gnu.org>
     [not found]         ` <87fxdivhki.fsf@arudy.ossau.uklinux.net>
2009-06-30 22:17           ` Neil Jerram
2008-05-28 14:02 ` 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=49dd78620805280659x37405d88l4e67ec7ba56a0934@mail.gmail.com \
    --to=neiljerram@googlemail.com \
    --cc=guile-user@gnu.org \
    --cc=trog24@comcast.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).