Re: [Tack-devel] ACK compiles on NetBSD-macppc, sort of...

[David G. <dg...@co...>]

Gregory T. (tim) Kelly wrote:
[...]
> Posts are coming through now.  I think the problem was my posting so so=
on after subscribing.  Is it better to email the list directly (and not c=
c you) or to cc it (and direct emails to you)?

Mail the list, please...

[...]
> Can llgen be extended to dynamic linking?  Or is it already?  Or am I
> identifying the wrong executable as the linker?  I'm also looking at
> replacing ld(1)  (well, the whole toolchain, to be honest).

Well, llgen doesn't know anything about dynamic linking because, er,
it's not the linker --- it's a parser generator like yacc. The tool you
want is led (Link Editor).  Look at util/led/led.6 for more information.

led only produces ack.out files; it took me a while to figure this out
--- if you want any other format, including a straight memory dump, you
need a converter. mach/arm/cv/cv.c is a ack.out to RiscOS converter ---
given that RiscOS binaries are straight memory dumps, you might be able
to use this if you want to generate simple images...

As for dynamic linking --- don't know. Way beyond my knowledge, I'm
afraid. It *ought* to be possible to take a partially linked image and
generate, say, an ELF executable of the right format so ld.so will load
dynamic libraries, but I don't have enough knowledge right now to make
any useful comments as to how.

Incidentally, your comments about magic characters in awk files ring a
bell, and I'm pretty sure I've fixed that; but it may not be in CVS yet.
(SF's CVS repository seems to have ground to a halt at the moment.)

--=20
+- David Given --McQ-+ "You cannot truly appreciate _Atlas Shrugged_
|  dg...@co...    | until you have read it in the original Klingon."
| (dg...@ta...) | --- Sea Wasp on r.a.sf.w
+- www.cowlark.com --+