From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24350 invoked by alias); 7 Mar 2017 01:59:20 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 24257 invoked by uid 89); 7 Mar 2017 01:59:18 -0000 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=intimate, billinghurst, Billinghurst, H*MI:sk:583230d X-HELO: sasl.smtp.pobox.com Received: from pb-smtp1.pobox.com (HELO sasl.smtp.pobox.com) (64.147.108.70) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 07 Mar 2017 01:59:16 +0000 Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id CC304734A0 for ; Mon, 6 Mar 2017 20:59:14 -0500 (EST) Received: from pb-smtp1.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id C48DF7349F for ; Mon, 6 Mar 2017 20:59:14 -0500 (EST) Received: from [192.168.1.4] (unknown [76.215.41.237]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp1.pobox.com (Postfix) with ESMTPSA id 4040E7349E for ; Mon, 6 Mar 2017 20:59:14 -0500 (EST) 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> <583230d9-f45c-aaa0-ed77-5c50863406f5@gmail.com> From: Daniel Santos Message-ID: <9b872914-d9cf-378e-6eec-96c175a61ffe@pobox.com> Date: Tue, 07 Mar 2017 01:59:00 -0000 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 X-Pobox-Relay-ID: AA1EA6EE-02D9-11E7-B348-97B1B46B9B0B-06139138!pb-smtp1.pobox.com X-IsSubscribed: yes X-SW-Source: 2017-03/txt/msg00081.txt.bz2 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