he loop ran through
very quickly. To get better statistics, I added a program like you
describe after each compilation. This has the effect of forcing the
(presumably damaged) gcc executable out of the memory buffer and a
reload of a fresh copy from disk, so the loop could continue.
BTW, can someon
/System.map-2.0.27 and the booted kernel are a matched set, they were
both created by one invocation of make-kpkg. What went wrong?
I have lsof 3.65-5 and kernel-package 3.19 installed, with dpkg-gencontrol
patched as described by Manoj Srivastava in his message of 12 Feb 1997.
--
Klaus Wacker
2 matches
Mail list logo