Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Message-ID: <426EDFD8.2F244F24@dessent.net>
Date: Tue, 26 Apr 2005 17:42:00 -0700
From: Brian Dessent <brian AT dessent DOT net>
Organization: My own little world...
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Any fix to cygheap_fixup_in_child failure after rebaseall?
References: <B7392353E4C4DE4ABC4EC255DB4CA04061C8B3 AT EXCHVS1 DOT spimageworks DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

Bruce Dobrin wrote:

> OK, that seems to have worked.   I've only used it alone or rebase for
> specific files before.  I generated a file from a find of all dll's
> under /usr and /lib ( then removed the cygwin1.dll from the list).  Can
> I assume the redundancy of hitting most of these 2 times will not have
> any adverse effect?  With all the stuff I compile on this machine I'm
> not sure how else to find them otherwise...

That's not how you use it.  rebaseall already knows where to find all
installed DLLs.  The only time you should ever use -T is to supply it
with *extra* DLLs that you have installed outside of setup.exe.

Though it looks like it will work okay your way, since it will just
rebase those DLLs a second time, but it's ugly.  You could avoid the
double rebasing by either a) adding a "sort -u" to rebaseall after it
has merged the two file lists, or b) skip rebaseall and call rebase
directly with your filelist.

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/