public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Daniel Santos <daniel.santos@pobox.com>
To: cygwin@cygwin.com
Subject: Re: Strange errors running gcc tests on Cygwin
Date: Mon, 13 Mar 2017 16:35:00 -0000	[thread overview]
Message-ID: <9b62f080-94f1-74d9-36ec-869e9490db2f@pobox.com> (raw)
In-Reply-To: <87pohp6jvk.fsf@Rainer.invalid>

On 03/10/2017 12:56 PM, Achim Gratz wrote:
> Brian Inglis writes:
>> Ensure that all Cygwin dlls including anything you build are included
>> in every rebase, and do an incremental rebase after every build.
> Don't do this, it's not what incremental rebase is for.  I've
> specifically implemented the "ephemeral" option to rebase to temporarily
> deal with DLL in staging directories without polluting the global rebase
> map.  The rebase map is still used if you specify that in order to work
> around the address space used by the installation, but the newl rebased
> libraries don't get recorded there.  Since that rebase is throw-away you
> have to specify all the ephemeral DLL that can potentially collide in
> each invocation of rebase.  That's still easier than doing a full rebase
> once you're done building.

Well this is interesting.  What happens if there is a collision? Will a 
detailed error message exist anywhere (syslogs, NT's event log, etc.)?

So when I run gcc's bootstrap, I'm building dlls that sit (temporarily) 
in the build directory.  If I do not explicitly rebase these, can I end 
up with collisions if I try to use them?

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

  parent reply	other threads:[~2017-03-13 16:35 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
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 [this message]
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=9b62f080-94f1-74d9-36ec-869e9490db2f@pobox.com \
    --to=daniel.santos@pobox.com \
    --cc=cygwin@cygwin.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).