X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=xNYQEx6lUWaiY9Cz
	B5z2LO9XLXeoPeBMGJomzx2PVa4wvae60xy2OePmgIm882PvhStB6CsY9Ewfcp18
	9F6B2AqsE1gLp9zMIFCxbjn/rWwxGkHOOKJEtWA+bIzub1Mi4zRW8JuFTpZESiOm
	RWHunLfIE6SYulqZ/8IBXeQ1gXk=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=lLbXWRQlj7DXLnwEbG0nKo
	tMHnQ=; b=OVUnk+RLHW0cxaZP/1BemUeIEm13kmrSqEK1ZD+3C/XXmivwPd9AlW
	BcLM001MMBylNg9je90HXeY0dJloeLGocH/X9lNxoU5COJ+CGn6dvmPpXrMdbkM1
	LbqVnIlUcb6jlSFTmZbpxaEkllmbn5LPE2eML2l2LdI7s1AakRp/g=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 spammy=H*MI:sk:ab35a49, H*i:sk:ab35a49, H*f:sk:ab35a49, study
X-HELO: sasl.smtp.pobox.com
Subject: Re: Strange errors running gcc tests on Cygwin
To: cygwin AT cygwin DOT com
References: <8fa02a72-e684-2ead-eacb-a5347d7594ae AT pobox DOT com> <82b31abc-7b7f-8f13-fc22-521c9ef84abf AT pobox DOT com> <8bda181f-f0bc-b0dc-2d2d-1bb17031ccee AT gmail DOT com> <b6c0f704-1f04-63ea-8220-ee30d623a9d6 AT pobox DOT com> <583230d9-f45c-aaa0-ed77-5c50863406f5 AT gmail DOT com> <9b872914-d9cf-378e-6eec-96c175a61ffe AT pobox DOT com> <ab35a49e-93e3-4384-bf81-3e8ac99b7194 AT gmail DOT com>
From: Daniel Santos <daniel DOT santos AT pobox DOT com>
Message-ID: <7372df4f-c55d-f9a3-325d-3f8800d67d98@pobox.com>
Date: Tue, 7 Mar 2017 17:25:26 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1
MIME-Version: 1.0
In-Reply-To: <ab35a49e-93e3-4384-bf81-3e8ac99b7194@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Pobox-Relay-ID: C4CE8FC8-038C-11E7-ADFF-FC50AE2156B6-06139138!pb-smtp2.pobox.com
X-IsSubscribed: yes

On 03/07/2017 07:58 AM, cyg Simple wrote:
> On 3/6/2017 9:03 PM, Daniel Santos wrote:
>> On 03/05/2017 05:08 AM, David Billinghurst wrote:
>>> No.
>>>
>>> LD_LIBRARY_PATH is used by dlopen ().
>>>
>>> PATH is one of the locations searched by Windows when starting
>>> applications, see https://msdn.microsoft.com/en-us/library/7d83bc18.aspx
>> Thank you for this clarification.  So load-time dlls are resolved (in
>> ntdll.exe or some such) using PATH and run-time dlls loaded with
>> dlopen() are resolved with LD_LIBRARY_PATH?  I'm obviously not intimate
>> with Cygwin's architecture, but I'm guessing that explicitly using
>> LoadLibrary is still going to use PATH.
> You're obviously not intimate with Windows either.  The search algorithm
> in Windows is more involved than PATH.  You need to study more.
>
My concern is with the dynamic portion of this behavior -- what is 
affected by environment variables.

--
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