Re: Strange errors running gcc tests on Cygwin

[Daniel Santos <daniel.santos@pobox.com>]

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