From: jont AT harlequin DOT co DOT uk (Jon Thackray)
Subject: Bad linker behaviour
6 Oct 1997 09:31:49 -0700
Message-ID: <199710061558.QAA08198.cygnus.gnu-win32@zaphod.long.harlequin.co.uk>
To: gnu-win32 AT cygnus DOT com

I have to assume the following behaviour is deliberate on the part of
the linker. Can it be turned off? What's the purpose of it? It's bad
news as far as I'm concerned, as it inhibits me from providing symbols
like free from other dlls (I get a message about can't find
_imp(double, long float, ...)() which is where I started). Globally
exchanging aa for bb in the program below allows a correct no errors
link.

	.text
	.global	__imp__bb
_bb:	jmp	*__imp__bb
__imp_bb:	ret

bash$ as -o poo.o poo.s
bash$ ld -o poo.dll --dll poo.o -e _bb
poo.o(.text+0x2):fake: undefined reference to `_imp(bool, bool)'
-
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".