Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: <42D86681.7010601@cwilson.fastmail.fm> Date: Fri, 15 Jul 2005 21:44:33 -0400 From: Charles Wilson User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) 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> In-Reply-To: <42D85D8E.2000207@familiehaase.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Gerrit P. Haase wrote: > Gerrit P. Haase wrote: > >> Hi all, >> >> I try to integrate --enable-auto-image-base with the Gnome packages. >> However I have some problems with the auto-image-base flag. Yes, it appears that I was wrong here: http://cygwin.com/ml/cygwin-apps/2005-07/msg00134.html I really don't know when --image-base=0x1000000 crept back in. Or maybe the patch that removed it got dropped and I never noticed 'cause things were working. Sorry for the confusion. > The promised patch is attached. > ACK. However, I'm waiting for a real resolution on the underlying question of what to do about DLL image bases. It seems that auto-image-base, even with the recent binutils fix, is only a stop gap measure. 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 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? If so, I'll happily patch libtool to conform, but I think it might be premature to do so now. -- Chuck -- 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/