From:	ian AT cygnus DOT com (Ian Lance Taylor)
Subject:	Re: what can link.exe do that cygwin32-ld can't ?
14 Jul 1997 13:24:31 -0700 :
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<199707141822.LAA25992.cygnus.gnu-win32@rtl.cygnus.com>
Original-To:	sos AT prospect DOT com DOT ru
Original-CC:	gnu-win32 AT cygnus DOT com
In-reply-to:	<01BC9047.8464FD60@sos> (message from Sergey Okhapkin on Mon, 14
	Jul 1997 11: 17:23 +0400)
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

   From: Sergey Okhapkin <sos AT prospect DOT com DOT ru>
   Date: Mon, 14 Jul 1997 11:17:23 +0400

   Ian Lance Taylor wrote:
   >    and if so, does this fix makeing .reloc dll's & exe's
   >    with B18?
   >
   > Doesn't that have more to do with running ld and dlltool multiple
   > times?

   Three-pass linking is very slow :-( For example, while building cygwin.dll 
   with full debug info, every ld pass tooks more than 1 minute on my P133/32M 
   NT4.0. The ld.exe process takes about 10M memory while running! It's 
   difficult to debug the stuff with long build times...

Yes.  I believe the correct fix is to incorporate the dlltool
functionality into the linker.  At least when building a DLL, the
operation is really no different than building an ELF or SunOS shared
library, which the linker can already do (in fact, DLL's are simpler
than ELF shared libraries).

The way to tackle this project is to examine the ELF linker, as used
on, e.g., Linux, understand how it works, and copy the general
approach for use when building a DLL.

Ian
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -