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=crzqMwCSMaDU2K1/ RpvCEitpOhssG3kpgKkrEtXCsRhQ1N40bDpMqsoCf4aCEa7yV7ALk/Sh1CKxLWIU nTRbL+LbG9ZZ+Noyyn2odVazG/MWgGQtP8H2ZTrZlv2ZpRjGwNCTKRwDTpVlTRDy FDv8knZU8twv6SanyVza1hWzjMk= 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=tZp93KCWoVMEyBJ96KWFYG Oc2yw=; b=rGgeJQHgKXKMPDKjmFs3pqR/ALhea1t6M6eNEpj+++4Hxm33Q/TyeV HSwan7f0Qyhmw8WXYmp22JBF1uzuha4/gZ7k+Oli1ZSpaLVCdPyWNamLkC8bagWd QL9lefGaVztOPcoLgJJM2Nglq123FuECJjxSjGjXD5bzgJpXKFhYI= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 spammy= X-HELO: sasl.smtp.pobox.com Subject: Re: Strange errors running gcc tests on Cygwin To: 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> <583230d9-f45c-aaa0-ed77-5c50863406f5 AT gmail DOT com> <9b872914-d9cf-378e-6eec-96c175a61ffe AT pobox DOT com> <7372df4f-c55d-f9a3-325d-3f8800d67d98 AT pobox DOT com> <937197c6-f0cd-a7a0-a12f-d3f943ba2c1d AT SystematicSw DOT ab DOT ca> <53efff58-2f84-123a-95a4-a7c426c003ce AT SystematicSw DOT ab DOT ca> <87pohp6jvk DOT fsf AT Rainer DOT invalid> From: Daniel Santos Message-ID: <9b62f080-94f1-74d9-36ec-869e9490db2f@pobox.com> Date: Mon, 13 Mar 2017 11:39:31 -0500 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: <87pohp6jvk.fsf@Rainer.invalid> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Pobox-Relay-ID: 0BD1969A-080B-11E7-AA29-97B1B46B9B0B-06139138!pb-smtp1.pobox.com X-IsSubscribed: yes 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