From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-developers@cygwin.com
Subject: Re: About the dll search algorithm of dlopen
Date: Mon, 22 Aug 2016 18:49:00 -0000 [thread overview]
Message-ID: <20160822184857.GC2971@calimero.vinschen.de> (raw)
In-Reply-To: <4d4481ce-c163-0ec9-29f5-59bbe13260fa@ssi-schaefer.com>
[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]
Hi Michael,
On Aug 22 14:15, Michael Haubenwallner wrote:
> For dlopen, it is more important to find the same dll file as would be
> found when the exe was linked against that dll file, rather than using
> the Linux-known algorithm and environment variables - and differ from
> process startup: Both really should result in the same algorithm here,
> even if that means some difference compared to Linux.
IMHO there is no good reason to have a DLL in a 3rd party subdir which
is available as system DLL. DT_RPATH/DT_RUNPATH semantics are not
created to overload system DLLs, rather to add a safe search path. Why
would you want to install a system DLL under the same name and thus the
same version in a non- system dir and expect the application to load
that? Ultimately this is bound to becoming outdated, fail if the
dependencies of the system DLL change, etc.
Even *if* we add the application dir adding it to dlopen should be
configurable, not statically, invisible under the hood.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-08-22 18:49 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 6:39 Michael Haubenwallner
2016-06-01 11:09 ` Corinna Vinschen
2016-06-01 14:25 ` Michael Haubenwallner
2016-06-01 20:18 ` Corinna Vinschen
2016-06-01 23:29 ` Yaakov Selkowitz
2016-08-19 16:37 ` Michael Haubenwallner
2016-08-19 16:39 ` Michael Haubenwallner
2016-08-20 19:32 ` Corinna Vinschen
2016-08-22 12:15 ` Michael Haubenwallner
2016-08-22 12:48 ` Peter Rosin
2016-08-22 13:01 ` Michael Haubenwallner
2016-08-22 16:02 ` About the dll search algorithm of dlopen (patch-r2) Michael Haubenwallner
2016-08-22 18:37 ` Corinna Vinschen
2016-08-23 8:16 ` Corinna Vinschen
2016-08-25 17:48 ` About the dll search algorithm of dlopen (patch-r3) Michael Haubenwallner
2016-08-26 10:59 ` Corinna Vinschen
2016-08-26 11:18 ` Corinna Vinschen
2016-08-26 11:49 ` Corinna Vinschen
2016-08-29 16:50 ` Michael Haubenwallner
2016-08-30 14:51 ` Corinna Vinschen
2016-08-30 15:57 ` Michael Haubenwallner
2016-08-31 18:48 ` Corinna Vinschen
2016-09-01 8:58 ` Michael Haubenwallner
2016-08-26 14:08 ` Michael Haubenwallner
2016-08-30 13:26 ` Corinna Vinschen
2016-08-26 12:04 ` Corinna Vinschen
2016-08-29 9:24 ` Michael Haubenwallner
2016-08-30 13:35 ` Corinna Vinschen
2016-08-30 16:41 ` Michael Haubenwallner
2016-08-31 18:43 ` Corinna Vinschen
2016-08-22 18:49 ` Corinna Vinschen [this message]
2016-08-23 8:55 ` About the dll search algorithm of dlopen Michael Haubenwallner
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160822184857.GC2971@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-developers@cygwin.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).