Michael Vanier <[EMAIL PROTECTED]> writes:
> I'm pretty happy to see guile catching up with other scripting languages.
> I'm especially happy with how easy it is to write extensions; I don't know
> of any other scripting language that has such a trivially simple extension
> mechanism.
I'm very h
That fixed it. I still had to specify the .so extension, but that's OK for
now. I didn't even have to specify an LTDL_LIBRARY_PATH environment
variable ;-)
I'm pretty happy to see guile catching up with other scripting languages.
I'm especially happy with how easy it is to write extensions; I
Michael Vanier <[EMAIL PROTECTED]> writes:
> Well, it's even more hosed that you realize :-(
Oops, did you configure Guile with "--enable-ltdl-install"? Sorry, I
forgot to tell you about this.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
Michael Vanier <[EMAIL PROTECTED]> wrote:
> Well, it's even more hosed that you realize :-( When I do what you say, it
> reports that it can't find libguile-bessel.so in /usr/lib. When I copy
> libguile-bessel.so into /usr/lib, it reports that it can't find it in
> /usr/local/lib (the next path
Well, it's even more hosed that you realize :-( When I do what you say, it
reports that it can't find libguile-bessel.so in /usr/lib. When I copy
libguile-bessel.so into /usr/lib, it reports that it can't find it in
/usr/local/lib (the next path in my LD_LIBRARY_PATH). And so forth. When
I ma
Michael Vanier <[EMAIL PROTECTED]> writes:
> I have put the file into /usr/lib and it still couldn't find it!
This is (another) bug in libltdl. It first tries the ".la" extenstion
and then should continue with the ".so" extension. However, it
incorrectly stops when no ".la" file could be found
Hi,
I've been walking through the guile info documentation, specifically the
section on defining your own guile extensions. This is for guile-1.6
running on a Debian GNU/Linux system. I am unable to get guile to find the
location of the shared library that I created (libguile-bessel.so). I ha
