Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT cygwin DOT com Message-ID: <3C7C6F5F.8020003@ece.gatech.edu> Date: Wed, 27 Feb 2002 00:32:15 -0500 From: Charles Wilson User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20010914 X-Accept-Language: en-us MIME-Version: 1.0 To: Robert Collins CC: cygwin-apps AT cygwin DOT com Subject: Re: setup.exe rebase patch References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-milter (http://amavis.org/) Robert Collins wrote: > >>-----Original Message----- >>From: Christopher Faylor [mailto:cygwin-apps AT cygwin DOT com] >> > >>However, I agree that rebasing shouldn't be the default >>behavior. In fact, I wonder if I should make cygwin >>non-rebaseable. It would load faster if I did that. >> > > Yes, and it would solve some of the nasty faults -auto-image-base. (The strange behaviour of often choosing a base that collides with cygwin). > > Rob > Note: libtool-devel does not use auto-image-base. I don't THINK libtool-stable does, either. And all of "my" DLLs have been rebuilt over the last several months without auto-image-base. Just FYI. Also, there was some code passed back and forth a while ago (Rob, yours maybe?) that purported to add a "non-relocatable" option to binutils. I don't remember the specifics, but I think there were some problems with that particular implementation. A working version that added a "non-relocatable" option to ld when creating a DLL would be a nice addition to binutils. Anybody remember more about this? I'm drawing a blank... --Chuck