From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21369 invoked by alias); 13 Mar 2017 16:35:22 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 19194 invoked by uid 89); 13 Mar 2017 16:35:22 -0000 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 Received: from pb-smtp1.pobox.com (HELO sasl.smtp.pobox.com) (64.147.108.70) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 13 Mar 2017 16:35:21 +0000 Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 002378182E for ; Mon, 13 Mar 2017 12:35:19 -0400 (EDT) Received: from pb-smtp1.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id EBE958182D for ; Mon, 13 Mar 2017 12:35:19 -0400 (EDT) Received: from [192.168.1.4] (unknown [76.215.41.237]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp1.pobox.com (Postfix) with ESMTPSA id 5019C8182C for ; Mon, 13 Mar 2017 12:35:19 -0400 (EDT) Subject: Re: Strange errors running gcc tests on Cygwin To: cygwin@cygwin.com References: <8fa02a72-e684-2ead-eacb-a5347d7594ae@pobox.com> <82b31abc-7b7f-8f13-fc22-521c9ef84abf@pobox.com> <8bda181f-f0bc-b0dc-2d2d-1bb17031ccee@gmail.com> <583230d9-f45c-aaa0-ed77-5c50863406f5@gmail.com> <9b872914-d9cf-378e-6eec-96c175a61ffe@pobox.com> <7372df4f-c55d-f9a3-325d-3f8800d67d98@pobox.com> <937197c6-f0cd-a7a0-a12f-d3f943ba2c1d@SystematicSw.ab.ca> <53efff58-2f84-123a-95a4-a7c426c003ce@SystematicSw.ab.ca> <87pohp6jvk.fsf@Rainer.invalid> From: Daniel Santos Message-ID: <9b62f080-94f1-74d9-36ec-869e9490db2f@pobox.com> Date: Mon, 13 Mar 2017 16:35:00 -0000 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 X-SW-Source: 2017-03/txt/msg00158.txt.bz2 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