The update listing reports:
> mycroft
> Sat May 28 22:11:34 PDT 1994
> Update of /b/source/CVS/src/sys/arch/m68k/fpsp
> In directory sun-lamp.cs.berkeley.edu:/d/users/mycroft/src/sys/arch/m68k/fpsp
> 
> Modified Files:
> 	fpsp.U 
> Log Message:
> Fresh compilation, with a few bugs fixed.

but now the magic number has changed from "NetBSD/m68k object file not
stripped" to "NetBSD/m68k4k object file not stripped" and ld refuses to
touch it (muttering about it not being a native object file).

What is a "m68k4k"? A typo of "m68k40" (68040) or something like that?

I edited the magic number to conform to that of all of the other object
files I had, and then linking proceeded fine (well, with the exception
of those retina files included by config.new). The resulting kernel
however ran some binaries, and not others. The changed mmap call is not
what seems to be the problem (my binaries are too old for that and use
what now probably is called ommap), but perhaps floating point is.

Some that worked: init, ls, bash, cat, mount, ldd.
Some that didn't: more, vi, od. (These didn't produce any output at all
and just terminated)
Trying ktrace and kdump to find which system call (if any) would be
the problem didn't help; perhaps the log file format changed, in any case
kdump complained about the log file.

The relevant kernel source was supped 6 june; the binaries are very old
(shared lib rev 4)

-Olaf.
--
___ Olaf 'Rhialto' Seibert                                 rhialto@mbfys.kun.nl
\X/ An original idea. That can't be too hard. The library must be full of them.

------------------------------------------------------------------------------