From: Daniel Santos <daniel.santos@pobox.com>
To: JonY <10walls@gmail.com>
Cc: Tim Prince <n8tm@aol.com>, cygwin@cygwin.com
Subject: Re: Strange errors running gcc tests on Cygwin
Date: Sun, 05 Mar 2017 04:20:00 -0000 [thread overview]
Message-ID: <bb343976-2680-3537-b517-e566a79bc914@pobox.com> (raw)
In-Reply-To: <8bda181f-f0bc-b0dc-2d2d-1bb17031ccee@gmail.com>
On 03/04/2017 09:46 PM, JonY wrote:
> Cygwin does NOT use LD_LIBRARY_PATH, Cygwin uses PATH like all Windows
> programs. It is one aspect that does not conform to *nix expectations.
Wonderful, this simplifies it greatly! I was wondering why the dlls
were under /usr/bin. :) Anyway, I'm waiting for the gcc bugzilla
database to come back up and I'll file the bug.
> Running tests under Cygwin is also complicated by the condition all DLLs
> do not get rebased at runtime, or a fork() can fail.
>
>> This further implies that, if it is looking in the local environment for
>> a library and not the build tree, then *all* test results could be
>> invalid due to it using compilers and libraries locally installed rather
>> than from the build tree, which would be very bad -- a regression that
>> hides other regressions!
>>
>> As much as I just want to get my own tests done, I suppose I better
>> debug this. *sigh*
>>
>> Daniel
>>
>>
> I suppose you can try to run s/LD_LIBRARY_PATH/PATH/g to see how it goes.
Well since I've gone this far I might as well come up with a patch for
the problem as well. Luckily, I somehow made a mistake about the
problem *not* happening on my first run of tests because I double
checked and it did! I guess the compare_tests script isn't perfect.
Also, I should make certain that this doesn't affect other tests (for
instance, we need to be certain that we're loading the correct libgcc).
Thanks 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
next prev parent reply other threads:[~2017-03-05 4:20 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 [this message]
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
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=bb343976-2680-3537-b517-e566a79bc914@pobox.com \
--to=daniel.santos@pobox.com \
--cc=10walls@gmail.com \
--cc=cygwin@cygwin.com \
--cc=n8tm@aol.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).