delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1999/10/11/20:01:54

From: Fokkema DOT DBRA AT delorie DOT com, 1043730 <dfokkema AT cs DOT vu DOT nl>
Newsgroups: comp.os.msdos.djgpp
Subject: object formats
Date: Mon, 11 Oct 1999 13:55:08 GMT
Organization: Fac. Wiskunde & Informatica, VU, Amsterdam
Lines: 18
Message-ID: <7tsq7s$n6s@cs.vu.nl>
NNTP-Posting-Host: galjas.cs.vu.nl
X-Newsreader: TIN [version 1.2 PL2]
X-Poster-Key: sha1:VbS1SaCDp0DsSX7Vksp+99bNhz8=
Cancel-Lock: sha1:pnQ26T0t4BRqKyy7er0hg06nRb0=
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Hi there!

I have a problem with object file formats. I managed to define a global
variable with the size of the output file in a linker script. The problem
is that I want a nasm file to use it. It isn't a problem to get a djgpp
c program to use it, nor to get a nasm coff-style object file to use it,
but it is to get a nasm a.out-style object file to use it. I can't use
the coff-style format because that doesn't support 16bit code and I want to
write a loader (I already have, actually). So I want to use an a.out file.
Now ld links it allright, but doesn't pay attention to symbols that are
used within that file. When I use objdump -i, I get errors that the 
a.out-i386 format has an invalid header. Is this related to my problem? If so,
or not so, can anyone please help me to get a nasm file use a global symbol
defined in a ld linker script?

Thanx,

David Fokkema

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019