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:references:to:reply-to:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=FmlgOCO6AaA/3fsr
	hx9g/CyI5lPWRphg3nP7VqPc033Bzhm1bY/UqLuiRsGofYkWxi1VVPK2TJ7sUt0k
	klJKHHj/yYvsKB2AhQoPhHY4bISXqhxzjRnIBp1KZ0ZEaQwb8tYDIqbh1Zm4cNMa
	17bNH27RAiuSrolk5vBogLkeqeg=
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:references:to:reply-to:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=y3XBRBQGzRBxXIRVM9x/9D
	/Xb4Y=; b=xS0dcsknWmO5I+HavyYBXmIoL2SsNPx2b3RLF4wAo4V3hGhwCwbHAp
	D7zq3wi5FhuIuFiYYGZQ4jH5cXlJZdWKpndMjMVoxZkF4VEKGQlkF6E5ebLsw4NC
	X5syGfwzss8APxsYwJavasEWRdz/qU1WPJGQqWryxVszxowrrjObQ=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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=0.4 required=5.0 tests=AWL,BAYES_20,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=H*R:D*ca, Hx-spam-relays-external:sk:smtp-ou, H*RU:sk:smtp-ou, HX-HELO:sk:smtp-ou
X-HELO:	smtp-out-no.shaw.ca
X-Authority-Analysis:	v=2.2 cv=P9pKvmIu c=1 sm=1 tr=0 a=WqCeCkldcEjBO3QZneQsCg==:117 a=WqCeCkldcEjBO3QZneQsCg==:17 a=IkcTkHD0fZMA:10 a=kcw_IJbkv-7SLZGDywcA:9 a=QEXdDO2ut3YA:10
Subject:	Re: Strange errors running gcc tests on Cygwin
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> <b6c0f704-1f04-63ea-8220-ee30d623a9d6 AT pobox DOT com> <583230d9-f45c-aaa0-ed77-5c50863406f5 AT gmail DOT com> <9b872914-d9cf-378e-6eec-96c175a61ffe AT pobox DOT com> <ab35a49e-93e3-4384-bf81-3e8ac99b7194 AT gmail DOT com> <7372df4f-c55d-f9a3-325d-3f8800d67d98 AT pobox DOT com> <aab8c02e-2fe7-8ebf-5f3b-126e0ea0a745 AT gmail DOT com> <a7aca745-bbf2-a356-704a-4956ae6a28b3 AT pobox DOT com> <937197c6-f0cd-a7a0-a12f-d3f943ba2c1d AT SystematicSw DOT ab DOT ca> <affe4ca0-4677-6eb9-1d7d-94a129adc30c AT pobox DOT com> <53efff58-2f84-123a-95a4-a7c426c003ce AT SystematicSw DOT ab DOT ca> <87pohp6jvk DOT fsf AT Rainer DOT invalid>
To:	cygwin AT cygwin DOT com
Reply-To:	Brian DOT Inglis AT SystematicSw DOT ab DOT ca
From:	Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Message-ID:	<29a5e139-0ac7-fdcc-27d3-3bec97209d63@SystematicSw.ab.ca>
Date:	Fri, 10 Mar 2017 13:29:56 -0700
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version:	1.0
In-Reply-To:	<87pohp6jvk.fsf@Rainer.invalid>
X-CMAE-Envelope:	MS4wfKirmUY3m5b7j6z9CGSBl47aXnuimLO/qOgbKJUGIYJ4Ssv0TYMvLyDOyNgwmkCRpQAolf/wGUbL8B0gsnhYlXsyvRVeFlrZHisf7vk/Z7faftlLfsc7 X2yWxg3LOVa3HAtvbMZkWFd2puZB3zFdJ9J/aKrKsCbNx9Q0ZUbAAZx6MVFoK/h+G6NnfK/FmTvn7Q==
X-IsSubscribed:	yes

On 2017-03-10 11:56, 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.

Has that been released yet or is it implied in options -O --oblivious 
and -T --filelist=FILE as documented in NEWS?

$ uname -srvmo
CYGWIN_NT-10.0 2.7.0(0.306/5/3) 2017-02-12 13:18 x86_64 Cygwin
$ rebase --version
rebase version 4.4.2 (imagehelper version 0.11)

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

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

- Raw text -