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~~~~^^^^~~~~~--~~~~~~~~~~~~~~~+
+~~~~~~~
