From: ludo@gnu.org (Ludovic Courtès)
To: bug-guile@gnu.org
Subject: Re: undefined __rl_init_argument on Mac OS 10.4
Date: Tue, 23 Jun 2009 17:15:38 +0200 [thread overview]
Message-ID: <868wjjf0bp.fsf@gnu.org> (raw)
In-Reply-To: 1D7A8E0B-5BFC-4F91-83F1-A05DF2DABF71@gmail.com
Hi,
Abdulaziz Ghuloum <aghuloum@gmail.com> writes:
> I tried building guile 1.9 today and the build fails due to undefined
> "__rl_init_argument". This appears to be defined in line 96 of guile-
> readline/readline.c and used only once in like 125 of the same file.
> Commenting out both lines makes the build proceed, but I don't know
> how bad this is. There are also a bunch of warnings about redefined
> bindings. A summary of the failed build log is below.
Can you please make sure you use GNU Readline and not BSD Editline's
broken compatibility layer? The `FAQ' file contains an entry on this
topic.
Thanks,
Ludo'.
next prev parent reply other threads:[~2009-06-23 15:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 5:48 undefined __rl_init_argument on Mac OS 10.4 Abdulaziz Ghuloum
2009-06-23 15:15 ` Ludovic Courtès [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-06-22 20:50 Abdulaziz Ghuloum
2009-06-23 14:49 ` dsmich
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=868wjjf0bp.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bug-guile@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).