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: <435FFA43.ED99088B@dessent.net>
Date: Wed, 26 Oct 2005 14:50:59 -0700
From: Brian Dessent <brian AT dessent DOT net>
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: cygwin-setup & rebaseall
References: <SERRANO4A2DreBBsQwY0000021e AT SERRANO DOT CAM DOT ARTIMI DOT COM>  <Pine DOT LNX DOT 4 DOT 64 DOT 0510251143120 DOT 10534 AT asterix> <435EE2BE DOT 86691C8F AT dessent DOT net> <Pine DOT LNX DOT 4 DOT 58 DOT 0510260938470 DOT 17311 AT harley DOT mcs DOT anl DOT gov>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

Satish Balay wrote:

> According to Jason's post, --enable-auto-image-base is been in use for
> a while.  [Since python doesn't always work without rebaseall] - is
> there some other issue with this approach? [mabye some dependent
> package should be built with --enable-auto-image-base - but it isn't?]

It is used for python itself, but it's not used for DLLs in other
packages that python modules might load.  That is why you still have to
rebaseall for python to work.  In order to completely retire rebaseall,
*every* package that contains a DLL must be compiled with this option.

Of course in reality, not every DLL necessarily *has* to be rebased,
only those that might be dynamically loaded at runtime, and even then
it's not always necessary.  But it's hard to determine which particular
cases those might be, and so in the general case you have to assign a
unique base address to every DLL.

> So if rebase is done - any package with a dll would have to trigger a
> rebase? I agree - if every update would trigger this - its not good.

Given the current method that rebaseall uses, yes, in theory it is
necessary to rerun rebaseall any time any DLL is modified.  But in
practice of course this is not true - as evidenced by the fact that many
(most?) cygwin users never even have to deal with rebasing.  This is why
it's so much easier to say "run rebaseall if/when you get this error"
than to definitively and automatically solve the problem so that it has
no possibility of ever occuring.

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/