From: Andy Wingo <wingo@pobox.com>
To: bug-libtool@gnu.org
Cc: bug-guile@gnu.org
Subject: Re: documentation / behavior discrepancy with lt_dlopenext
Date: Wed, 30 Mar 2011 23:36:23 +0200 [thread overview]
Message-ID: <m31v1o1eaw.fsf@unquote.localdomain> (raw)
In-Reply-To: <20110330192025.GG7627@gmx.de> (Ralf Wildenhues's message of "Wed, 30 Mar 2011 21:20:25 +0200")
Greets Ralf,
On Wed 30 Mar 2011 21:20, Ralf Wildenhues <Ralf.Wildenhues@gmx.de> writes:
> * Andy Wingo wrote on Wed, Mar 30, 2011 at 07:19:18PM CEST:
>> "/usr/lib64/libSDL-1.2.so.0.11.3".
>
> Well, I'd kinda argue that that file has a library extension, but after
> that extension, there's version the info extension. This is common for
> several systems (e.g., GNU/Linux, Solaris).
Sure, that's probably right. However it's tough to tell. You could
look for "\.so(\.|$)" or something. But that's encoding lots of
details.
I think that uses of dlopenext are already oblivious to `stat' calls,
because they sanction looking for .la files before e.g. .so files, so
it's not a problem to just do what the doc says: bare path first, then
grovel extensions.
MHO :)
Cheers,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-03-30 21:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 17:19 documentation / behavior discrepancy with lt_dlopenext Andy Wingo
2011-03-30 19:20 ` Ralf Wildenhues
2011-03-30 21:36 ` Andy Wingo [this message]
2011-03-31 1:31 ` Bob Friesenhahn
2011-03-31 8:33 ` Andy Wingo
2011-07-01 15:03 ` 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=m31v1o1eaw.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=bug-guile@gnu.org \
--cc=bug-libtool@gnu.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).