SUMMARY: building kernel after upgrade 5.1 -> 5.1a

From: Alex Harkema <HarkemaA_at_vertis.nl>
Date: Tue, 23 Oct 2001 14:34:12 +0200

Bryan Lavelle had the solution!

---
Check in /sys/<HOSTNAME> and /sys/kern for files with dates of 1 Jan 1970.
If there, touch them with a current date and retry the doconfig.
---
Indeed, there were a lot of files of that date! Even /usr was.
After a find /usr/sys -exec touch {} \;
the doconfig didn't fail.
Now I'm running the new kernel! Still, isn't that something to worry about,
not being able to build a new kernel after I upgraded? Or was something
already not okay on my system?
Thanks
Alex
-----Original Message-----
From: Alex Harkema [mailto:HarkemaA_at_vertis.nl]
Sent: Tuesday, October 23, 2001 1:33 PM
To: 'tru64-unix-managers_at_ornl.gov'
Cc: 'kevin.Jones_at_compelsolve.co.uk'
Subject: failure building kernel after upgrade 5.1 -> 5.1a
Hi all, 
(ref:
http://www.ornl.gov/its/archives/mailing-lists/tru64-unix-managers/2001/10/m
sg00393.html ) 
I am one of those, encountering the same problems after upgrading from 5.1
to 5.1a 
I don't know why the kernel build fails after upgrade, but following happens
when rebuilding the kernel:
/usr/sbin/doconfig builds in /usr/sys/SYSNAME the new kernel. 
There is also the Makefile. In the makefile is an entry for lockinfo.c. It
seems like the make fails, because it cannot locate the lockinfo file in
/sys/kern/ 
That's why doconfig fails (don't know how to make lockinfo.c) I cannot think
of any reason why this fails after the upgrade to v5.1a, before it never
seemed to cause any problems...
Any ideas? 

Received on Tue Oct 23 2001 - 12:36:07 NZDT