From:	"Chris Burgess" <jazz AT uknet DOT demon DOT co DOT uk>
Newsgroups:	comp.os.msdos.djgpp
Subject:	ld (that comes with djgpp) major problems
Date:	Wed, 23 Dec 1998 09:04:16 -0000
Message-ID:	<914404117.2848.0.nnrp-09.c1ed260d@news.demon.co.uk>
NNTP-Posting-Host:	uknet.demon.co.uk
X-NNTP-Posting-Host:	uknet.demon.co.uk:193.237.38.13
X-Trace:	news.demon.co.uk 914404117 nnrp-09:2848 NO-IDENT uknet.demon.co.uk:193.237.38.13
X-Complaints-To:	abuse AT demon DOT net
X-Newsreader:	Microsoft Outlook Express 4.72.3155.0
X-MimeOLE:	Produced By Microsoft MimeOLE V4.72.3155.0
Lines:	33
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

When I am linking two or more coff format files together with ld using this
command:
 ld -T kernel.ld <OBJS>

and that file is (kernel.ld):
OUTPUT_FORMAT("coff-go32")
ENTRY(start)
SECTIONS
{
  .text: {
    *(.text)
  }
  .data : {
    *(.data)
  }
  .bss : {
    *(.bss)
    *(.comm)
  }
}

I end up with a huge bunch of junk in the final file (the coff files are
compiled/assembled from both NASM and DJGPP) - this junk is generally taken
from some file somewhere on the disk. I've checked all my disks - no errors,
can anyone explain???
I hope so! I need it to work!


Thanks

Chris

- Raw text -