On 09/01/2018 09:36 PM, Ken Moffat via blfs-dev wrote:
On Sun, Sep 02, 2018 at 01:38:36AM +0100, Ken Moffat via blfs-dev wrote:
I guess this probably belongs on -support, but I'll ask here first.
Tried building 8.3, except with a 4.14.67 kernel and headers this
week, on a box which usually runs as a desktop but is temporarily
configured as a server (to check for problems before doing a real
upgrade).
1. /var/lib/hwclock
For some reason /var/lib/hwclock does not exist, so I figured this
must be a kernel .config problem. Went into the kernel, but make
menuconfig moaned that I needed ncurses-dev : there was a similar
fix for 4.19-rc1 in the past day or so. When I built the kernel for
the first time I zcat'd /proc/config.gz to .config and made
oldconfig.
Anyway, all the expected RTC options appear to be present.
Looking at my latest 8.3-rc2 desktop, with 4.18.5, I see that there
too /var/lib/hwclock is missing - the difference is that I haven't
tried to shut that down, I hibernate it.
I've created a patch to the sysv bootscript to hopefully shut up the
error message:
--- setclock.orig 2018-09-02 03:15:49.591619721 +0100
+++ setclock 2018-09-02 03:16:34.638823114 +0100
@@ -49,6 +49,7 @@
stop)
log_info_msg "Setting hardware clock..."
+ mkdir -p /var/lib/hwclock
hwclock --systohc ${CLOCKPARAMS} >/dev/null
evaluate_retval
;;
No idea if it will help.
Not needed. Created in Chapter 6, util-linux.
But as to the ncurses-dev problem, I wonder if it was because I
built the kernel as root. Trying 'make menuconfig' on a virgin
4.18.5 on a desktop has no problem. Using a virgin 4.14.67 as a
user was "interesting" - untar 4.14, cd, try to apply 4.14.67 patch,
after a few files it started to tell me the patch would create a
documentation file which already existed (at least two files, then
I gave up - the second was for l1tf which is not in 4.14.0).
Blew that away, fresh 4.14 extract, dry run of patch ok, applied ok.
And menuconfig works.
Perhaps I was trying to run menuconfig as a user in a directory
owned by root, and inability to write was the actual error. But the
initial problem applying part of the patch is disconcerting.
Yes, I've run into that before. Generally 'chown me.me -R .' in the
kernel source directory should clear things up.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
