This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
Re: --enable-runtime-pseudo-reloc support in cygwin, take 3.
- From: egor duda <deo at logos-m dot ru>
- To: Matt <matt at use dot net>
- Cc: cygwin-developers at cygwin dot com
- Date: Tue, 3 Dec 2002 11:33:06 +0300
- Subject: Re: --enable-runtime-pseudo-reloc support in cygwin, take 3.
- Organization: deo
- References: <Pine.NEB.4.30.0212021129140.12738-100000@cesium.clock.org>
- Reply-to: egor duda <cygwin-developers at cygwin dot com>
Hi!
Monday, 02 December, 2002 Matt matt@use.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@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19