public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: David Billinghurst <dbcygwin@gmail.com>
To: cygwin@cygwin.com, Daniel Santos <daniel.santos@pobox.com>
Subject: Re: Strange errors running gcc tests on Cygwin
Date: Wed, 08 Mar 2017 00:36:00 -0000	[thread overview]
Message-ID: <aab8c02e-2fe7-8ebf-5f3b-126e0ea0a745@gmail.com> (raw)
In-Reply-To: <7372df4f-c55d-f9a3-325d-3f8800d67d98@pobox.com>

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

  reply	other threads:[~2017-03-08  0:36 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-04  5:44 Daniel Santos
2017-03-04 11:27 ` Tim Prince via cygwin
2017-03-05  2:49 ` Daniel Santos
2017-03-05  3:49   ` JonY
2017-03-05  4:20     ` Daniel Santos
2017-03-05  7:23     ` Daniel Santos
2017-03-05  7:32     ` Daniel Santos
2017-03-05 11:08       ` David Billinghurst
2017-03-07  1:59         ` Daniel Santos
2017-03-07 13:58           ` cyg Simple
2017-03-07 23:21             ` Daniel Santos
2017-03-08  0:36               ` David Billinghurst [this message]
2017-03-08  5:14                 ` Daniel Santos
2017-03-08  8:21                   ` Brian Inglis
2017-03-09 22:48                     ` Daniel Santos
2017-03-09 23:51                       ` Brian Inglis
2017-03-10  0:01                         ` Tim Prince via cygwin
2017-03-10 18:56                         ` Achim Gratz
2017-03-10 20:30                           ` Brian Inglis
2017-03-10 20:48                             ` Achim Gratz
2017-03-13 16:35                           ` Daniel Santos
2017-03-13 17:25                             ` Marco Atzeri
2017-03-15 16:50                               ` Daniel Santos
2017-03-15 19:36                                 ` Brian Inglis
2017-03-16 20:55                                   ` Daniel Santos
2017-03-17  5:17                                     ` Brian Inglis
2017-03-18 13:48                                       ` Daniel Santos
2017-03-18 14:52                                         ` cyg Simple
2017-03-12  4:04                         ` Daniel Santos

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aab8c02e-2fe7-8ebf-5f3b-126e0ea0a745@gmail.com \
    --to=dbcygwin@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=daniel.santos@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).