[I'm not on this list, so please cc me.]
It seems guile-1.8.7 does not admit dynamic library file name
extensions .dylib, but only .so, on Mac OS X (tried 10.5.8. PPC G4),
despite the manual saying guile should adapt to local standards. The
example in the manual sec. 4.2.1 works fine with
Hello,
Hans Aberg writes:
> It seems guile-1.8.7 does not admit dynamic library file name
> extensions .dylib, but only .so, on Mac OS X (tried 10.5.8. PPC G4),
> despite the manual saying guile should adapt to local standards. The
> example in the manual sec. 4.2.1 works fine with
> gcc -dyna
On Jan 30, 2010, at 09:41, Hans Aberg wrote:
[I'm not on this list, so please cc me.]
It seems guile-1.8.7 does not admit dynamic library file name
extensions .dylib, but only .so, on Mac OS X (tried 10.5.8. PPC G4),
despite the manual saying guile should adapt to local standards. The
exam
Hello Hans,
On Sat 30 Jan 2010 15:41, Hans Aberg writes:
> It seems guile-1.8.7 does not admit dynamic library file name extensions
> .dylib, but only .so, on Mac OS X (tried 10.5.8. PPC G4)
I think your example shold work, but it's something that's totally
handled by libltdl. Are you using the
On 30 Jan 2010, at 19:37, Ludovic Courtès wrote:
The abstraction over file name extensions is handled by Libtool’s
libltdl, used in ‘libguile/dynl.c’. Which version of Libtool/ltdl are
you using?
I took down the latest stable before trying to compile guile:
libtool --version
ltmain.sh (GN
On 30 Jan 2010, at 19:39, Ken Raeburn wrote:
The Mac OS X situation is a bit more complicated than on "normal"
ELF-based UNIX systems; shared libraries and dynamically loadable
objects are not the same thing. It's easy to assume they're
equivalent when working mostly on ELF or Windows syst
On 30 Jan 2010, at 20:30, Andy Wingo wrote:
It seems guile-1.8.7 does not admit dynamic library file name
extensions
.dylib, but only .so, on Mac OS X (tried 10.5.8. PPC G4)
I think your example shold work, but it's something that's totally
handled by libltdl. Are you using the latest libltd
