INSTALL file explains how this information is supposed to be delivered
to libltdl (with LD_LIBRARY_PATH). No information about how this
information is supposed to be found by configure.ac/Makefile.am in
extension. Neither in documentation of guile nor in code of existing
extensions.
Vorfeed Canal [EMAIL PROTECTED] writes:
now what I need to do to
install guile 1.8.1 as /usr/bin/guile-1.8.1 and guile 1.8.2 as
/usr/bin/guile-1.8.2
Install under different $prefix.
Where configure.ac/Makefile.am
should put libmysuperextension.la (+ .so, etc) file ?
Under the $prefix of
Vorfeed Canal [EMAIL PROTECTED] writes:
GUILE=/myexperiments/guile/bin/guile \
GUILE_CONFIG=/myexperiments/guile/bin/guile-config \
GUILE_TOOLS=/myexperiments/guile/bin/guile-tools \
I would set the PATH, this probably works though.
$ /myexperiments/guile/bin/guile -c '(use myextension
[EMAIL PROTECTED] (Ludovic Courtès) writes:
In fact, Libtool's versioning mechanism already makes this possible for
programs: the loader and/or dynamic linker chooses the one version of
the library the program expects to be linked against.
Oh, well, libtool only wraps what ld.so does, but
Hi,
Kevin Ryde [EMAIL PROTECTED] writes:
Remember if you want to call a C code module directly from a C
mainline then you need something the ordinary loader can cope with
too.
(If setting up something clean and portable for this stuff was easy it
would have already been done.)
You're
Vorfeed Canal [EMAIL PROTECTED] writes:
On 9/29/05, Ludovic Courtès [EMAIL PROTECTED] wrote:
So, I'm all in favor of having your patch (or something equivalent)
applied. I guess you'll need to /kindly/ ask the developers for further
reviewing and see what needs to be done so that it can
Hi Vorfeed,
Vorfeed Canal [EMAIL PROTECTED] writes:
4. Actual contents of default directory list is not important. Only
two requirements:
A. It must not be empty - this way there are place to put default
libraries like readline.
B. It must be modifyable at runtime - this way complex
Hi,
Vorfeed Canal [EMAIL PROTECTED] writes:
Of course it must - how else can it load them ? With my patch it knows
about few default places and can be instructed about other places in
nice shemely way.
Yes, your patch seems to be one possible solution. However, why not use
`pkglibdir'
