From nobody Thu Jan 12 16:31:59 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Nt9795LdZz2p4Rn for ; Thu, 12 Jan 2023 16:32:05 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Nt9790wzfz3sKw for ; Thu, 12 Jan 2023 16:32:04 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Authentication-Results: mx1.freebsd.org; none Received: from kalamity.joker.local (123-1-88-210.area1b.commufa.jp [123.1.88.210]) (authenticated bits=0) by www121.sakura.ne.jp (8.16.1/8.16.1/[SAKURA-WEB]/20201212) with ESMTPA id 30CGVxXH066330; Fri, 13 Jan 2023 01:31:59 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Fri, 13 Jan 2023 01:31:59 +0900 From: Tomoaki AOKI To: freebsd-current@freebsd.org Cc: garyj@gmx.de Subject: Re: Build failure: main-n259988-48dc9150ac36 -> main-n260011-40bb52c89b87 Message-Id: <20230113013159.a7ec78f73b613f8c23bf21c5@dec.sakura.ne.jp> In-Reply-To: <20230112154119.380d6208@ernst.home> References: <20230111143214.6c703b2b@ernst.home> <20230112154119.380d6208@ernst.home> Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.0) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4Nt9790wzfz3sKw X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Thu, 12 Jan 2023 14:41:19 +0000 Gary Jennejohn wrote: > On Thu, 12 Jan 2023 03:44:03 -0800 > David Wolfskill wrote: > > > On Wed, Jan 11, 2023 at 07:12:46AM -0700, Warner Losh wrote: > > > looks like we may need another 'unclean' workaround for this? > > > > > > Warner > > > > > > On Wed, Jan 11, 2023 at 6:32 AM Gary Jennejohn wrote: > > > ... > > > > I had this problem also. After deleting obj/usr the buildworld succeeded. > > > > > > > .... > > > > Empirically: > > rm -fr /usr/obj/usr/src/amd64.amd64/usr.sbin/zic > > > > got through the issue on my build machine. (I expect that it will also > > do so on the others where I track head, but they are presently building > > lang/rust.) > > > > Perhaps an UPDATING entry would suffice? > > > > Didn't work for me when I decided to update my laptop, which had rather > old /usr/src contents. I ended up deleting obj/usr again. > > I installed the new world on my tower this morning. Now I see a new > problem. > > I don't know whether this new problem is related to the new tzcode, but > apps like gkrellm2 and xclock now display the time one hour earlier > than the actual time output by date(1), e.g. 10AM rather than 11AM. > > I had to set my /etc/localtime to GMT+0 to get the correct time output > even though I live in Germany and the correct value would be either > Europe/Berlin or CET. > > My laptop, which still has the old tzcode installed, did not exhibit > that weird error. > > -- > Gary Jennejohn Do you have /etc/wall_cmos_clock? Otherwise, FreeBSD base system thinks that the CMOS clock is set to UTC. A blank file (just `touch`ed to create) is enough. IIUC, your laptop has it, but your tower has none. -- Tomoaki AOKI