Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Date: Tue, 3 Dec 2002 11:33:06 +0300 From: egor duda Reply-To: egor duda Organization: deo X-Priority: 3 (Normal) Message-ID: <16369457584.20021203113306@logos-m.ru> To: Matt CC: cygwin-developers AT cygwin DOT com Subject: Re: --enable-runtime-pseudo-reloc support in cygwin, take 3. In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi! Monday, 02 December, 2002 Matt matt AT use DOT net wrote: M> On Mon, 2 Dec 2002, egor duda wrote: >> CF> I'm also not sure that this is a great idea for mingw, which is supposed >> CF> to be a pretty generic windows environment, AFAIK. If mingw starts >> CF> creating fancy new dlls then that sort of strays from their core >> CF> purpose, IMO. >> >> Why? It's obvious for mingw people to implement, say, openssl library >> as a dll. It exports several data items. Mingw version of ssl.dll >> would export them. Now, imagine that someone writes an application >> which uses data items exported from ssl.dll and compiles in with >> mingw. If _pei386_runtime_relocator is linked within application and >> called at startup, then all references from foo.exe to ssl.dll which >> have to be fixed up, will be. >> >> The core idea of _pei386_runtime_relocator() is to be generic, as long >> as PE on i386 is concerned, hence the name. For instance, i don't see >> much difficulties for interix to use it too. M> Having a proper reloc section would help be one step closer to running M> cygwin and mingw programs under Purify. This makes it worthwhile, in my M> opinion. It's not a proper reloc section. It's pseudo-relocation section, so, i afraid they won't help in case of purify. Egor. mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19