From: Linas Vepstas <linasvepstas@gmail.com>
To: 宋文武 <iyzsong@member.fsf.org>
Cc: Maurizio Boriani <baux@gnu.org>,
guix-devel@gnu.org, Guile User <guile-user@gnu.org>
Subject: Re: guile-dbi: Use libltdl and prefer GUILE_DBD_PATH.
Date: Mon, 10 Jul 2017 17:54:22 -0500 [thread overview]
Message-ID: <CAHrUA37z4SKjy=JWuSqT5Ucu0if3MtbmxrqTn0hqYRz153n=2w@mail.gmail.com> (raw)
In-Reply-To: <878tush5wx.fsf_-_@member.fsf.org>
Sorry for the very late reply. I applied these patches to
https://github.com/opencog/guile-dbi
which will have to serve as the official repo for guile-dbi, since gna.org
is now dead.
Maurizio Boriani, I was surprised to see you answer -- do you have some
other repo somwhere that contains the guile-dbi code?
--linas
On Thu, Sep 15, 2016 at 10:36 PM, 宋文武 <iyzsong@member.fsf.org> wrote:
> Hi!
>
> To reall, curentlly, guile-dbi use dlopen to load its backends.
> So, for Guix we have to set LD_LIBRARY_PATH, which is not desired.
>
> > [...]
> > (me:)
> >> I think it will be great to introduce a new search path (eg:
> GUILE_DBD_PATH)
> >> in addition to LD_LIBRARY_PATH. Find the absolute so filepath in it
> >> ourself, then pass to dlopen.
> >
> > (ludo:)
> > Why not, but then it would be redundant with LD_LIBRARY_PATH and
> > LTDL_LIBRARY_PATH, which would further complicate the search rules.
> >
>
> Yeah, but I just learn that libltdl has a convenient function to do
> this..
>
>
> So, here are patches for using libltdl and a new search path:
>
>
>
> Hope they are obvious :-)
>
>
next prev parent reply other threads:[~2017-07-10 22:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87bn2yc3zu.fsf@member.fsf.org>
[not found] ` <878ty06ze8.fsf@gnu.org>
[not found] ` <8760t36it3.fsf@elisya.g.zucchetti.com>
[not found] ` <87mvme8w8k.fsf@gnu.org>
[not found] ` <87inx2inou.fsf@member.fsf.org>
[not found] ` <87fus6mfbe.fsf@gnu.org>
2016-09-16 3:36 ` guile-dbi: Use libltdl and prefer GUILE_DBD_PATH 宋文武
2016-09-16 6:57 ` baux
2017-07-10 22:54 ` Linas Vepstas [this message]
2017-07-11 11:02 ` 宋文武
2017-07-11 18:31 ` Nala Ginrut
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHrUA37z4SKjy=JWuSqT5Ucu0if3MtbmxrqTn0hqYRz153n=2w@mail.gmail.com' \
--to=linasvepstas@gmail.com \
--cc=baux@gnu.org \
--cc=guile-user@gnu.org \
--cc=guix-devel@gnu.org \
--cc=iyzsong@member.fsf.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).