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=I5fvpLNtrMk2I6Ub
	uJm+QaYdk3txrn2MFU4P+1G4W+YVGCIxcXcDAkvBO8FZljKpsbctlmGgylzKBUtU
	rOrCXBLaKFbMIq6YYGGV03aVA+IeEhUiBa+dvJoMMNPUURnuGVbiVlN2F+BX7Ukc
	+3v8uS6PfnGupc6kQe0sTIPVS5s=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: Strange errors running gcc tests on Cygwin
To: cygwin@cygwin.com
References: <8fa02a72-e684-2ead-eacb-a5347d7594ae@pobox.com> <82b31abc-7b7f-8f13-fc22-521c9ef84abf@pobox.com> <8bda181f-f0bc-b0dc-2d2d-1bb17031ccee@gmail.com> <b6c0f704-1f04-63ea-8220-ee30d623a9d6@pobox.com> <583230d9-f45c-aaa0-ed77-5c50863406f5@gmail.com>
From: Daniel Santos <daniel.santos@pobox.com>
Message-ID: <9b872914-d9cf-378e-6eec-96c175a61ffe@pobox.com>
Date: Mon, 6 Mar 2017 20:03:21 -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: <583230d9-f45c-aaa0-ed77-5c50863406f5@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

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.

So it seems that libgcc on Cygwin is called cyggcc_s-seh-1.dll on lives 
in /usr/bin.  This makes the gcc test harness's attempt to switch 
between host and target compilers problematic because we can't remove 
/usr/bin from the PATH.  We can can prepend the built-tree's path, but 
it's still a bit unsettling that, if something goes wrong with the 
build-tree, we can still end up loading the installed libgcc instead of 
failing.  Still, it will be better than the current situation.

Thank you for your help with this.

Daniel


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