From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19788 invoked by alias); 13 Mar 2017 17:25:43 -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 19775 invoked by uid 89); 13 Mar 2017 17:25:42 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=H*i:sk:9b62f08, H*f:sk:9b62f08, H*MI:sk:9b62f08, risk X-HELO: mail-wm0-f42.google.com Received: from mail-wm0-f42.google.com (HELO mail-wm0-f42.google.com) (74.125.82.42) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 13 Mar 2017 17:25:41 +0000 Received: by mail-wm0-f42.google.com with SMTP id n11so45948206wma.1 for ; Mon, 13 Mar 2017 10:25:41 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=VaEnaxdKXAA642pwTOl8Vx3W4hjFA5OvDC31nzo8ElI=; b=RTo+2zSAJVhmDvpowJ7zxpg6bPexFKmEoNqxUTTbOpj0xfpOwo+JgF8KyVn4EpVQIX hKCZVCdA/JSltltqFwKc9JmUGm8hvFuEsgJY60wzudDqnjQEQwouUJLLTvZPk6UR9fOb ckGUdP/UVaNYLu/bmnxTd9dIUOzOF4iVaiS29WIvA59BoEvT1dUZTnQx9rLDUbWCeKAM bXNVHOr3SDsVZLIqbN0kcLHdUXSG2XfBdP4BkN3ozIMjcfNMnrYWaS9BEfkWuGbDRTGS Uf/Yc6iuJfci/ibIDCpxRHhhUV/XyIFYlvJ7GrMt06daafbXHORM2DmCb9IVciohspHS OVlA== X-Gm-Message-State: AFeK/H1VYQx2169qXfdiJ1CjzaKsXdpGgHmxyanOtNhRvnbqTdOvadlEEyNGDyxL/Xgusg== X-Received: by 10.28.147.129 with SMTP id v123mr11370087wmd.51.1489425939586; Mon, 13 Mar 2017 10:25:39 -0700 (PDT) Received: from [172.21.188.226] ([149.6.156.42]) by smtp.googlemail.com with ESMTPSA id v18sm25811595wrc.41.2017.03.13.10.25.38 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 13 Mar 2017 10:25:38 -0700 (PDT) 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> <9b62f080-94f1-74d9-36ec-869e9490db2f@pobox.com> From: Marco Atzeri Message-ID: Date: Mon, 13 Mar 2017 17:25:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <9b62f080-94f1-74d9-36ec-869e9490db2f@pobox.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2017-03/txt/msg00159.txt.bz2 On 13/03/2017 17:39, Daniel Santos wrote: > 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? The risk of collision is very low on 64 bit. It is higher on 32 bit but as gcc don't depend on other libraries, I don't expect that to happen. If happens you can rebase in tree before running the tests, providing the list of new dll to rebase. I used it when I had problem on testing Octave; but Octave dlls with debugging symbols are huge and pull tons of other dlls so the collision was almost sure on 32bit > Thanks, > Daniel Regards Marco -- 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