From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: cong gu <gucong43216@gmail.com>
Cc: wingo@pobox.com, guile-user@gnu.org
Subject: Re: using GSL with cblas via FFI
Date: Mon, 04 Jun 2012 06:15:47 +0200 [thread overview]
Message-ID: <87d35fn24s.fsf@gnuvola.org> (raw)
In-Reply-To: <CAH_4JjMHzEQ42Mj1E8h=skudqSOihCrA9a3Br4AUbPz++PkE+w@mail.gmail.com> (cong gu's message of "Sun, 3 Jun 2012 17:04:29 -0500")
() cong gu <gucong43216@gmail.com>
() Sun, 3 Jun 2012 17:04:29 -0500
I found libtool offers a way to make a shared library globally
available. So I wrote a patch that provides `dynamic-link-global'.
A call like `(dynamic-link-global "libgslcblas")' should make
things work.
I don't know whether it is portable, though. Documentation of
libtool mentioned that not all loaders are able to act upon this
`advice'.
Aside from portability, there is also coherence in design to consider.
In (info "(libtool) Libltdl interface") i see seven funcs that take
‘lt_dladvise *ADVISE’:
lt_dladvise_init
lt_dladvise_destroy
lt_dladvise_ext
lt_dladvise_global
lt_dladvise_local
lt_dladvise_resident
lt_dladvise_preload
The first two manage the object; the last five mutate its internals.
Your proposal sequences ‘lt_dladvise_ext’ and ‘lt_dladvise_global’
with ‘lt_dlopenadvise’, essentially. This is fine for your needs
today, no doubt. How about further on, when you need _resident
or _preload, or _FOO (in some future libtool release), or when you
want _global but not _ext?
With five bits, you have 32 combinations (actually less, as not all
combinations are meaningful, e.g., _global and _local together). It
would be awkward to eventually find all these combinations wrapped
individually, in C and exposed to Scheme. What is a better way?
next prev parent reply other threads:[~2012-06-04 4:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-03 22:04 using GSL with cblas via FFI cong gu
2012-06-04 4:15 ` Thien-Thi Nguyen [this message]
2012-06-04 6:11 ` cong gu
2012-06-04 4:22 ` Thien-Thi Nguyen
-- strict thread matches above, loose matches on Subject: below --
2011-03-24 14:54 Johan Hidding
2011-03-25 20:31 ` Ludovic Courtès
2011-03-26 9:53 ` Johan Hidding
2011-03-31 15:18 ` Andy Wingo
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=87d35fn24s.fsf@gnuvola.org \
--to=ttn@gnuvola.org \
--cc=gucong43216@gmail.com \
--cc=guile-user@gnu.org \
--cc=wingo@pobox.com \
/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).