Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
Date: Mon, 2 Dec 2002 11:30:33 -0800 (PST)
From: Matt <matt AT use DOT net>
X-Sender:  <matt AT cesium DOT clock DOT org>
To: <cygwin-developers AT cygwin DOT com>
Subject: Re: --enable-runtime-pseudo-reloc support in cygwin, take 3.
In-Reply-To: <1879834601.20021202185923@logos-m.ru>
Message-ID: <Pine.NEB.4.30.0212021129140.12738-100000@cesium.clock.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

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.

Having a proper reloc section would help be one step closer to running
cygwin and mingw programs under Purify. This makes it worthwhile, in my
opinion.


--
http://www.clock.org/~matt