unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Roger Mc Murtrie <rogermc@iinet.net.au>
To: Gregory Marton <gremio@csail.mit.edu>
Cc: bug-guile@gnu.org
Subject: Re: Make problem Mac OS X
Date: Sat, 12 Jan 2008 06:26:37 +1100	[thread overview]
Message-ID: <F3A0C42A-A3E3-48A3-A742-A1864170592C@iinet.net.au> (raw)
In-Reply-To: <Pine.LNX.4.62.0801110754040.6071@ashmore.csail.mit.edu>

Hi Greg,
I've been using locate, find and grep to find missing bits and pieces.
Also the search function of Mac Finder windows (which doesn't seem to  
search all files)
On my machine
locate libltdl
produces
.
.
.
/usr/lib/libltdl.3.1.4.dylib
/usr/lib/libltdl.3.dylib
/usr/lib/libltdl.a
/usr/lib/libltdl.dylib
/usr/lib/libltdl.la

Perhaps for Debian you have to install it yourself. I think the   
libguile-ltdl is a separate thing.
Of course, to use libltdl.a you have to inclide -ltdl in your gcc link  
commands, usually by setting the environment variable before running  
configure:
LDFLAGS=-ltdl
export LDFLAGS
(Although for one package that I build, setting environment variables  
suggested by configure -help results in empty Makefiles!)
Googling libltdl leads to www.gnu.org/software/libtool. Looks like  
libltdl comes with GNU Libtool which I seem to remember having to  
install at some stage

I don't recall getting the  "you may need to run ldconfig". message,  
but I think I've had it from other installs in the past.
I never have found out how to use it. I think it comes from the loader  
and is really a message, perhaps, to gcc rather than humans.

I'm not much more than a "novice" myself, just stumble along with lots  
of trial and error.
Nowadays, package installation seems to involve one battle after  
another!

Good luck
Roger


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?
>
> Thanks for any help on this,
> Grem
>
>> Hi Roger,
>>
>> So I'm up against this problem now, and trying, as Ludovic  
>> suggests, to install the "real" GNU readline.  I downloaded,  
>> unpacked, configured, made, did sudo make install, and everything  
>> worked fine on my MacBook Pro running 10.4, but at the end it says  
>> "you may need to run ldconfig".  It appeared to install into /usr/ 
>> local/lib successfully.
>>
>> making in the guile directory still gives me this problem, as if it  
>> didn't notice.  Do you know what ldconfig this is of which it  
>> speaks, or how to run it?  Will it help guile recognize the one it  
>> wants?
>>
>> I'm a rank novice at all these things, sorry.
>>
>> Thanks,
>> Grem
>>
>> Roger Mc Murtrie whote on Wed, 09 Jan 2008 23:30:43 -0800
>>> 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'  
>>> the offending line of code. However, I don't know what impact it  
>>> would have, and that would really be a crude hack to work around  
>>> the defects of Editline's compatibility layer, so it's probably  
>>> better to leave things as is.
>>> Thanks, Ludovic.
>>> Perhaps, detect if `rl_pending_input' is available at configure- 
>>> time.
>>> If not, abort the configure with an appropriate message?
>>> Regards
>>> Roger
>>
>>
>>
>
> -- 
> ------ __@   Gregory A. Marton                http://csail.mit.edu/~gremio/
> --- _` 
> \<,_                                                                .
> -- (*)/ (*)          Quantum Physics: The dreams stuff is made of.
> ~~~~~~~~~~~~~~~~-~~~~~~~~_~~~_~~~~~v~~~~^^^^~~~~~--~~~~~~~~~~~~~~~+ 
> +~~~~~~~




  parent reply	other threads:[~2008-01-11 19:26 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             ` Roger Mc Murtrie [this message]
     [not found]               ` <Pine.LNX.4.62.0801120948290.23339@ashmore.csail.mit.edu>
2008-01-12 23:18                 ` Make problem Mac OS X Roger Mc Murtrie
2008-01-21 22:47               ` Neil Jerram
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=F3A0C42A-A3E3-48A3-A742-A1864170592C@iinet.net.au \
    --to=rogermc@iinet.net.au \
    --cc=bug-guile@gnu.org \
    --cc=gremio@csail.mit.edu \
    /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).