Message-ID: <000a01be4f73$ec893180$8fbc98ce@waldroni>
From: "Isaac Waldron" <waldroni AT lr DOT net>
To: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Cc: <djgpp AT delorie DOT com>
Subject: Re: Accessing Constants in Assembly Code
Date: Wed, 3 Feb 1999 07:51:29 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3155.0
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0
Reply-To: djgpp AT delorie DOT com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

- -----Original Message-----
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Isaac Waldron <waldroni AT lr DOT net>
Cc: djgpp AT delorie DOT com <djgpp AT delorie DOT com>
Date: Wednesday, February 03, 1999 5:15 AM
Subject: Re: Accessing Constants in Assembly Code


>
>On Tue, 2 Feb 1999, Isaac Waldron wrote:
>
>> The only line that accesses VideoRAM in blit.s appears as such:
>> 
>> mov eax,[_VideoRAM] (NASM syntax)
>
>Then why did the linker complain about VideoRAM, without the
>underscore?

I think that the linker takes off the underscore before reporting the
conflict.  When I compile a simple .c file that has no main function,
ld complains about undefined references to 'main', not '_main'.  So,
that would mean that when the linker gets to my blit.o file in the
library, there hasn't been a symbol called _VideoRAM defined yet.  But
that doesn't make any sense, because the symbol is defined in another
object file in the library!

Thanks again,
Isaac Waldron
-----BEGIN PGP SIGNATURE-----
Version: PGP Personal Privacy 6.0.2

iQA/AwUBNrhGUFvPBN9ggn+IEQKlpACgxyiYjGr7Daou9b35Kxzcabeu2eUAoIkg
+Mk2O9V4X1kwBxtFde7kx/Ak
=6OEt
-----END PGP SIGNATURE-----