Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!decwrl!sun!pitstop!sundc!seismo!uunet!mcvax!hp4nl!kunivv1!wn2!janhen
From: janhen@wn2.sci.kun.nl (Jan Hendrikx)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Anyone has the source of a good linker?
Summary: I'd like a 'standard' one
Message-ID: <342@wn2.sci.kun.nl>
Date: 20 Feb 89 16:49:08 GMT
References: <8902171605.AA16549@jade.berkeley.edu> <01k165dDlp10106aJkM@amdahl.uts.amdahl.com>
Organization: University of Nijmegen, The Netherlands.
Lines: 23

In article <01k165dDlp10106aJkM@amdahl.uts.amdahl.com>, shs@uts.amdahl.com (Steve Schoettler) writes:
> In article <8902171605.AA16549@jade.berkeley.edu> U211344@HNYKUN11.BITNET (Olaf 'Rhialto' Seibert) writes:
    [that's me, for the record]
> > ... we seem to be missing a linker with source.
> 
> Well, the gnu linker is available in binutils.tar.Z on prep.ai.mit.edu.
> Naturally, the output is in a.out (b.out) unix executable format.

Yes, and that is exactly the problem. I don't want to write some
patch programs that I must run before I can execute the program I just
linked. And (not being familiar with GNU ld) I assume it eats lots
of memory, and also only knows about the Unix-'Hunks' Text, Data and Bss.
No multiple code or data hunks. A third problem is that I don't have
the source here, and can't ftp.

> And of course, you could use
> gcc/gas/ld, which is why I suspect Olaf wanted a linker in the first place.

Actually, the idea was to use it with PDC/A68k, but the intention
is about the same.

> Steve
-Olaf Seibert (using Jan's account)