public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christian Franke <Christian.Franke@t-online.de>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.33-0.1
Date: Mon, 27 Oct 2014 06:31:00 -0000	[thread overview]
Message-ID: <544DE6C3.3080005@t-online.de> (raw)
In-Reply-To: <20141025144934.GB30397@calimero.vinschen.de>

Corinna Vinschen wrote:
> On Oct 25 13:10, Corinna Vinschen wrote:
>> On Oct 24 23:17, Denis Excoffier wrote:
>>> 2014-10-24 22:16, Christian Franke wrote:
>>>> Another possible solution:
>>>> Check for e.g. CYGWIN_DLLPATH environment variable before calling SetDllDirectory().
>>>>
>>>> If unset or empty, call SetDllDirectory("X:\path_to_cygwin\bin");
>>>> else if set to ".", do nothing.
>>>> else call SetDllDirectory(CYGWIN_DLLPATH);
>>>>
>>>> The above 'make check' should then work again as 'CYGWIN_DLLPATH=. make check'.
>>> I can buy this. Setting 'export CYGWIN_DLLPATH := .' at the beginning of the Makefile will
>>> do the job.
>>>
>>>> Possible enhancement: If AddDllDirectory() is available (>= Win8), accept a real search path in CYGWIN_DLLPATH.
>>> Also perhaps you can use yet another subitem in the CYGWIN environment variable?
>> If AddDllDirectory works without much hassle, which I have to test first,
>> why introduce CYGWIN_DLLPATH or another CYGWIN item?
>>
>> LD_LIBRARY_PATH would be the one we want then, wouldn't it?
> One really big problem with AddDllDirectory is this:  While you can add
> multiple directories to the search path, the order in which these
> directories are added does not specify a search order.  In fact, the
> order in which the paths are searched is unspecified per MSDN.
>
> In Denis example that means, if we add /usr/bin and /my/dir/bin to the
> DLL search path, Denis case works or it doesn't, and we never know when
> it will work and when it won't, and we have no way to influence this.
> Oh boy.
>
> Apart from SetDllDirectory and AddDllDirectory, what about this very
> simple solution in Cygwin:
>
> - Don't call SetDllDirectory at all, thus "." is kept in the search
>    path.
>
> - In execve, when creating the Windows environment for the child process,
>    check if $PATH is empty.  If so, set $PATH to /bin for the child.
>    Or, check if /bin is in $PATH, if not, add it.
>
> That would catch both problems, backward compatibility with Denis
> scenario, as well as the PATH setting in postfix.

OK for me. For postfix, the '$PATH is empty' check would be sufficient.

Christian


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  parent reply	other threads:[~2014-10-27  6:31 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-22  9:42 Corinna Vinschen
2014-10-22 13:35 ` Habermann, Dave (DA)
2014-10-22 13:54   ` Corinna Vinschen
2014-10-22 14:48     ` Corinna Vinschen
2014-10-22 16:44     ` Achim Gratz
2014-10-23 18:01       ` Achim Gratz
2014-10-24  9:56         ` Corinna Vinschen
2014-10-27 18:35     ` Habermann, Dave (DA)
2014-10-27 21:26       ` Corinna Vinschen
2014-10-28 13:42         ` Habermann, Dave (DA)
2014-10-28 14:20           ` Corinna Vinschen
2014-10-28 14:58             ` Eric Blake
2014-10-28 15:16               ` Corinna Vinschen
2014-10-28 17:07             ` Habermann, Dave (DA)
2014-10-28 20:22             ` Habermann, Dave (DA)
2014-10-29 10:21               ` Corinna Vinschen
2014-10-30 17:02                 ` David Rothenberger
2014-10-30 17:22                   ` Corinna Vinschen
2014-10-30 23:50                   ` Andrey Repin
2014-10-31 12:26                     ` Habermann, David (D)
2014-10-29  0:05         ` Andrey Repin
2014-10-27 21:35       ` Andrey Repin
2014-10-23  2:57 ` Tom Schutter
2014-10-23 15:44   ` Corinna Vinschen
     [not found]     ` <5449F281.3080701@cisra.canon.com.au>
2014-10-24  6:35       ` Luke Kendall
2014-10-24 10:37         ` Corinna Vinschen
2014-10-26 22:28           ` Luke Kendall
2014-10-27 12:39             ` Corinna Vinschen
2014-10-27 23:13               ` Luke Kendall
2014-10-23  3:00 ` Tom Schutter
2014-10-23  6:14   ` Corinna Vinschen
2014-10-23 18:00   ` Achim Gratz
2014-10-23 22:05   ` Andrey Repin
2014-10-23 18:06 ` Denis Excoffier
2014-10-24 11:02   ` Corinna Vinschen
2014-10-24 18:41     ` Denis Excoffier
2014-10-24 19:36       ` Corinna Vinschen
2014-10-24 20:16         ` Christian Franke
2014-10-24 20:45           ` Corinna Vinschen
2014-10-24 21:17           ` Denis Excoffier
2014-10-25 11:10             ` Corinna Vinschen
2014-10-25 14:49               ` Corinna Vinschen
2014-10-25 17:29                 ` Denis Excoffier
2014-10-25 18:15                   ` Corinna Vinschen
2014-10-27  6:31                 ` Christian Franke [this message]
2014-10-27 11:37                   ` Corinna Vinschen
2014-10-27 13:35                     ` Andrey Repin
2014-10-27 14:09                       ` Corinna Vinschen
2014-10-24 16:35 ` Andrey Repin
2014-10-24 17:28   ` Keith Christian
2014-10-24 17:57     ` Eric Blake
2014-10-26  3:11       ` Keith Christian
2014-10-24 18:16     ` Thomas Wolff
2014-10-24 19:17   ` Corinna Vinschen
2014-10-22 12:07 Angelo Graziosi
2014-10-22 12:37 ` Corinna Vinschen
2014-10-22 13:27 Angelo Graziosi
2014-10-22 13:41 ` Corinna Vinschen

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=544DE6C3.3080005@t-online.de \
    --to=christian.franke@t-online.de \
    --cc=cygwin@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).