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=ZjSGtBZn+rVADUjN
	wsOLD65JV0RuKXodG6YlGJeWH1FnS9zvmaHJQs7stYPh3azOPUvZX8QQtTGQjX8S
	dhz4JaKxvdIwQ4AJ9LjQUqJmHnHvpfQSEBcPAS2Bb10LZkjpsTq7bV6XZdjSqeIV
	yfq1lh3CD2t1pwnqjsVG/OOfwFg=
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=EJr3uhji+0Ul5Qxma3+mXe
	LTTFI=; b=qiP9tL/DVvIj6hiDaTuKQSI1TkT1WuvcFa9+s89be23UaTZTvL0/G8
	ojVhTZI+yhYRibt5tGIsTU1HNp1/R4Bf3//Y6GIAMW3DHyt37s5CIZYfQfXO9l9/
	yH31+ITCaJ9DqJKYe8ZSkRGafxwAz/WUqA4YyZed7y+QwVBKci3g0=
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=-1.4 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=dll, H*r:ip*192.168.1.37, H*MI:sk:7372df4, H*f:sk:7372df4
X-HELO: mail-pf0-f178.google.com
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=1e100.net; s=20161025;        h=x-gm-message-state:subject:to:references:from:message-id:date         :user-agent:mime-version:in-reply-to:content-transfer-encoding;        bh=wFJLM6Olf4/AaZx7l19+Di9LgLWvGNGy7xlurUwDcag=;        b=SEPxSc/gwCwZbeSzrq8I84ReoqPnf6fVuR0bTHgSnpLhZrcTKiE6s0xB3Fyr5SBUmj         mWmXEGi4tUptSB10FFSsb3jZnunoN06XZAkYgj7ay4eaWBF5sJeWqTFZ+ATaJQEMlPxG         L1EUHRfowAS6ITFWBrj/iMzDq22qlsFaKfD6uGo3PX3AXF7167yL6e6mYHeNYxEXvyR1         YsW0f4Mgiv+D5G0+6ACpBp2FwiE2xwx3JuEt+RGFbnGikiPTZB6M69Kp6zEip4iGWgN3         B3ncwpB7NJZLLjwkl9YEDHOqbNwQu6Leuk7gXenEi3+h9rzKE/h2HRK989N+oyIgWjB1         nTQg==
X-Gm-Message-State: AMke39kLBi8MiHBjnwyiD66nYforqD51GPf8lhUC72EJFkTBz2dxG7nJDrbMHz1B+WNLtw==
X-Received: by 10.84.174.131 with SMTP id r3mr4440972plb.30.1488933364493;        Tue, 07 Mar 2017 16:36:04 -0800 (PST)
Subject: Re: Strange errors running gcc tests on Cygwin
To: cygwin AT cygwin DOT com, Daniel Santos <daniel DOT santos AT pobox 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>
From: David Billinghurst <dbcygwin AT gmail DOT com>
Message-ID: <aab8c02e-2fe7-8ebf-5f3b-126e0ea0a745@gmail.com>
Date: Wed, 8 Mar 2017 11:36:00 +1100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <7372df4f-c55d-f9a3-325d-3f8800d67d98@pobox.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

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.





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