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=sVWMaj713bRIwt8x
	s2VmnKuU0hzxO895YMO7CkeRsbykb7QpnlMjYI79UcaTv6m7ilcoNli92mn1QkNb
	7FsFRayZQuCYagnCz+rQBw+oQ5qG8BZTzal7anY6zHQGbjb7+5b7z7rQrhb12j87
	ed8Q/eRWVKuMY0K/vDFBV6VH+7Y=
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=I6ntU8yqm3hKemZoBiD5+b
	ZrXaw=; b=VptmOK7vnI6UAU7KR7NNiAUBEVqLuRep7EOsMEFOExXc74SVMr5he/
	Wr3+RXHr3hSXFWUqsenJYf+5ns/vW/8dStNIAou4+Xi7XHIK1wpaLg3AF4vlomCG
	2bb56A+qRM6SdPht6a/sEZURdWEVt7QBOt58XSWG9P1NpA3z208Cs=
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=farm, 16k, UD:bat, pity
X-HELO: sasl.smtp.pobox.com
Subject: Re: Strange errors running gcc tests on Cygwin
To: David Billinghurst <dbcygwin AT gmail DOT com>, 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> <7372df4f-c55d-f9a3-325d-3f8800d67d98 AT pobox DOT com> <aab8c02e-2fe7-8ebf-5f3b-126e0ea0a745 AT gmail DOT com>
From: Daniel Santos <daniel DOT santos AT pobox DOT com>
Message-ID: <a7aca745-bbf2-a356-704a-4956ae6a28b3@pobox.com>
Date: Tue, 7 Mar 2017 23:18:09 -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: <aab8c02e-2fe7-8ebf-5f3b-126e0ea0a745@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Pobox-Relay-ID: 0B31B612-03BE-11E7-BED0-97B1B46B9B0B-06139138!pb-smtp1.pobox.com
X-IsSubscribed: yes

On 03/07/2017 06:36 PM, David Billinghurst wrote:
> On 8/03/2017 10:25, Daniel Santos wrote:
>
>> My concern is with the dynamic portion of this behavior -- what is 
>> affected by environment variables.
>
> Many years ago I ran a nightly build/test of gcc under cygwin and 
> reported the results to gcc-testresults.  There may be is discussion 
> on the gcc mailing lists from c2000-2005.  If you search 
> "site:gcc.gnu.org David Billinghurst cygwin" you ??might?? find 
> something relevant.
>
> From memory, I got it all working by
>
>  * building gcc and friends
>  * using find to locate all the .exe and .dll files in the build tree
>  * worked out by trial and error which files were needed at run time by
>    the test suite.
>  * setting PATH when running the testsuite so that the directories
>    containing (new) required .exe and .dll were in front of any system
>    directories
>  * making sure that PATH wasn't reset by the testsuite
>  * looking at places where LD_LIBRARY_PATH was set/modified by the
>    testsuite and checking if cygwin needed PATH to match
>  * (submitting patched to fix gcc testsuite under cygwin)
>
> Once that was done it all "just worked" until it broke again. Good luck.
>

Thank you very much for this. This is the path that I was kind-of 
setting off on, I just wanted to try one more time to run the tests 
as-is, this time with only one make job and see if I could get the mass 
of failures to match so that I could say that my patches cause "no 
additional errors" (ignoring the fact that there's 16k total failures), 
but I can't even get the breakages to match up.  (This is another topic, 
when I run tests in parallel I eventually end up with some "broken pipe" 
errors and that make job hangs).

I found some of your patches, pity it got re-broken.  I have a bug open 
for this here: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79867.  In 
the end, I think that this should be fixed by adding some new "black 
box" interfaces to DejaGnu that manage the executable and library search 
paths.  Then gcc's testsuite should deprecate ANY direct access to any 
of the *PATH environment variables in favor of this new interface in 
DejaGnu.  As it is, the gcc code already changes both LD_LIBRARY_PATH 
and SHLIB_PATH to support HP-UX (not sure if any other systems use the 
latter), so it's already gotten a little hairy.

In order to facilitate this cleanly, I think that libgcc needs to be 
moved out of /usr/bin and into /usr/lib/gcc/<triplet>/<version>/ and 
then have that added to the PATH and LD_LIBRARY_PATH somewhere 
(autoexec.bat? registry? I have no idea).  Having an /sbin/ldconfig 
would be the most ideal mechanism of managing this. (Anybody want a 
little project? :)  The test harness regularly toggles in between the 
host and target compiler.

We need a clean and reproducible set of steps for running tests on 
Cygwin.  Somewhere, these tests should be run regularly, maybe on a 
server/compiler farm somewhere under a VM, so that breakages can be 
addressed as soon as they appear rather than when somebody wants to 
touch the ms_abi code and has to test on Cygwin -- how I ended up here. :)

Thanks again for the help!
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