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: <42D8F0E2.3020105@familiehaase.de>
Date: Sat, 16 Jul 2005 13:34:58 +0200
From: "Gerrit P. Haase" <gerrit AT familiehaase DOT de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: enable-auto-image-base with libtool not working?
References: <42D857E2 DOT 6020609 AT familiehaase DOT de> <42D85D8E DOT 2000207 AT familiehaase DOT de> <42D86681 DOT 7010601 AT cwilson DOT fastmail DOT fm>
In-Reply-To: <42D86681.7010601@cwilson.fastmail.fm>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Charles Wilson wrote:

> cgf(?) has repeatedly stated that we'l run out of address space 
> eventually, whether we have some bureaucratic nightmare of a registry 
> for "approved" DLL base addresses, or toss everything in to the 
> auto-image-base hopper.

I think it was Jason.  Even if there are two or three DLLs using the
same base address, it should be better than all DLLs using the same
base.


> I still haven't seen a true "fix" for the issue proposed.  Is moving 
> forward with --enable-auto-image-base as a "policy" the best we can do?

I think so.

> If so, I'll happily patch libtool to conform, but I think it might be 
> premature to do so now.

What is the default base address used by ld if no base flag is used?
I.e. isn't specifying --image-base=0x1000000 redundant because it is
the dafault base address?


Gerrit
-- 
=^..^=

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