Path: utzoo!attcan!uunet!samsung!emory!mephisto!udel!mmdf
From: bunnell@henry.asel.udel.edu (Tim Bunnell)
Newsgroups: comp.os.minix
Subject: Installing PC 1.5.3
Message-ID: <11884@nigel.udel.EDU>
Date: 22 Feb 90 19:48:37 GMT
Sender: mmdf@udel.EDU
Lines: 19

To my considerable surprise, under 1.5.3 the command:

	ar q libc.a 'lorder *.s | tsort'

gives every appearance of actually working.  However, it reports a cycle
between malloc and memmove (the assembly version which also contains
an entry point to memcpy).  I have not been able to manually trace the cycle,
but in trying to do so I noticed that malloc has DEBUG code enabled.  Is this
the recommended setting for that routine at present?  Will anything break if
the debugging code is disabled?

By the way, apart from already reported problems and some errors that were
probably my own the 1.5.0 --> 1.5.3 upgrade has gone smoothly for the
commands and libraries.  Are we to rebuild the boot image and kernel using
the old kernel + new fs-mm-tools, or wait for the new kernel before taking
that step?

Tim Bunnell
<bunnell@asel.udel.edu>