guile-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: my load path bug


From: Andy Wingo
Subject: Re: my load path bug
Date: Mon, 19 Oct 2009 21:00:09 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.92 (gnu/linux)

Hello

On Mon 12 Oct 2009 21:11, address@hidden (Ludovic Courtès) writes:

> Ken Raeburn <address@hidden> writes:
>
>> Andy's patch (eb35012) adds $pkglibdir to the path searched for
>> libraries.  That directory is $prefix/lib/guile; it contains a
>> subdirectory "1.9" and nothing else.  The libguile-srfi-srfi-1-v-4.*
>> libraries guile searches for at startup are in $prefix/lib aka
>> $libdir.
>>
>> Changing SCM_LIB_DIR to be defined as $libdir instead of $pkglibdir is
>> easy enough, if the current location is where we want those
>> libraries.
>
> Yes, I think that’s the way to go, since libguile-srfi-*,
> libguilereadline*, etc. get installed to $(libdir), not $(pkglibdir).
>
> If nobody objects, please commit it.
>
>> Do we need programs to be able to link against them directly?
>
> Yes since people may be explicitly linking against them (they’ve always
> been under $(libdir)).
>
>> Do we need non-guile programs to be able to find them with dlopen?
>
> Yes.
>
>> (Is it too late to consider changing it?)
>
> Yes.

For the list: we worked out a compromise. Guile .so or .dylib extensions
may be installed in the $libdir or in the extensions dir, which by
default is $prefix/lib/guile/1.9/extensions. Check pkg-config
--variable=extensionsdir guile-2.0 for the exact value.

Andy
-- 
http://wingolog.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]