[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: guile and libtool versions
From: |
Luc, Kevin |
Subject: |
RE: guile and libtool versions |
Date: |
Mon, 19 Apr 2010 09:59:22 -0700 |
Hi guys,
Thanks for the responses. I had in fact built the latest libtool, but
I had forgotten to add it to the LD_LIBRARY_PATH, so I think the build
was finding some older version and linking against that, so at runtime
the versions were not matching.
I had a spelling mistake in specifying the prefix directory for
libtool, so the install was going into a different directory ("lib")
instead of the intended dir ("libs") ARGG!
Kevin.
-----Original Message-----
From: Andy Wingo [mailto:address@hidden
Sent: Saturday, April 17, 2010 3:56 AM
To: Luc, Kevin
Cc: address@hidden
Subject: Re: guile and libtool versions
Hi Kevin,
I suggest installing libtool-1.5.6 from your distro's packages, if
possible. Or better, libtool 2.2.6b from packages.
On Thu 15 Apr 2010 18:21, "Luc, Kevin" <address@hidden> writes:
> I have installed guile 1.8.7 and libtool-1.5.6. When I try to run
my test app I get the following error:
>
> error while loading shared libraries: libltdl.so.0: cannot open shared
object file: No such file or directory
Try running the equivalent of "ldd" on your binary, and on libguile.so,
to see what it's trying to pull in. You should get a message if your
system can't find libldtl.so.
> I also tried to create a symbolic link:
This way lies madness :) It's easy to mess up a system if you go too far
down this road.
Andy
--
http://wingolog.org/
This communication, including any attachments, may contain information that is
proprietary, privileged, confidential or legally exempt from disclosure. If
you are not a named addressee, you are hereby notified that you are not
authorized to read, print, retain a copy of or disseminate any portion of this
communication without the consent of the sender and that doing so may be
unlawful. If you have received this communication in error, please immediately
notify the sender via return e-mail and delete it from your system.