unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
To: Roger Mc Murtrie <rogermc@iinet.net.au>
Cc: bug-guile@gnu.org, Gregory Marton <gremio@csail.mit.edu>
Subject: Re: Make problem Mac OS X
Date: Mon, 21 Jan 2008 22:47:18 +0000	[thread overview]
Message-ID: <87d4rulrt5.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <F3A0C42A-A3E3-48A3-A742-A1864170592C@iinet.net.au> (Roger Mc Murtrie's message of "Sat, 12 Jan 2008 06:26:37 +1100")

Roger Mc Murtrie <rogermc@iinet.net.au> writes:

> I think the libguile-ltdl is a separate thing.

Yes, libguile-ltdl was a tweaked version of libltdl that we used
during the 1.6.x series, while waiting for upstream to make a fix that
we needed.  It isn't needed anymore.

> On 11/01/2008, at 11:56 PM, Gregory Marton wrote:
>
>> This is an ongoing problem -- now on Debian guile build complains of
>> not having libltdl even though 'sudo aptitude install libguile-
>> ltdl-1' claimed it was correctly installed.  How do I go about
>> finding where this libtdl has been put, and telling configure?

For building Guile 1.8.x on Debian, you need the libltdlN-dev package,
where N is a number.  I am using Debian etch, and have libltdl3-dev.

>>>> Ludovic wrote:
>>>> Then I guess MacOS X users had better install the "real" GNU
>>>> Readline. Alternatively, we could detect whether
>>>> `rl_pending_input' is available at configure-time, and `#ifdef'

How do we test for a library variable (i.e. rl_pending_input) in
configure.in ?

>>>> Perhaps, detect if `rl_pending_input' is available at configure-
>>>> time.
>>>> If not, abort the configure with an appropriate message?
>>>> Regards
>>>> Roger

That sounds good to me, if we can detect it.

Regards,
     Neil





  parent reply	other threads:[~2008-01-21 22:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-09  3:00 guile-1.8.3 Intel Mac Leopard compilation fails due to no off64_t Roger Mc Murtrie
2008-01-09  3:09 ` Roger Mc Murtrie
2008-01-10 18:40   ` Neil Jerram
2008-01-10 18:30 ` Neil Jerram
     [not found]   ` <881AD488-9F97-4F0D-B078-BEBD5BB684B8@iinet.net.au>
2008-01-10 22:53     ` Neil Jerram
2008-01-10 23:53       ` Roger Mc Murtrie
2008-01-10 23:59       ` Roger Mc Murtrie
     [not found]         ` <Pine.LNX.4.62.0801110725270.6071@ashmore.csail.mit.edu>
     [not found]           ` <Pine.LNX.4.62.0801110754040.6071@ashmore.csail.mit.edu>
2008-01-11 19:26             ` Make problem Mac OS X Roger Mc Murtrie
     [not found]               ` <Pine.LNX.4.62.0801120948290.23339@ashmore.csail.mit.edu>
2008-01-12 23:18                 ` Roger Mc Murtrie
2008-01-21 22:47               ` Neil Jerram [this message]
2008-01-22 22:10         ` guile-1.8.3 Intel Mac Leopard compilation fails due to no off64_t Neil Jerram
2008-01-22 22:57           ` Roger Mc Murtrie
2008-01-22 23:09             ` Neil Jerram
2008-01-22 23:42               ` Roger Mc Murtrie
2008-01-30 23:08           ` Neil Jerram
2008-01-30 23:10             ` Neil Jerram
  -- strict thread matches above, loose matches on Subject: below --
2008-01-10  7:29 Make problem Mac OS X Roger Mc Murtrie
2007-09-26 22:14 Hans Aberg
2007-09-27 14:49 ` Ludovic Courtès
2007-10-06 19:48   ` David Fang
2007-10-07 14:29     ` 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=87d4rulrt5.fsf@ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --cc=bug-guile@gnu.org \
    --cc=gremio@csail.mit.edu \
    --cc=rogermc@iinet.net.au \
    /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).