Is it now safe to attempt updating current with UFS?SincerelyFilippo
On Wednesday, June 1, 2022 at 01:07:20 AM GMT+2, Warner Losh
wrote:
On Tue, May 31, 2022 at 3:55 PM Olivier Cochard-Labbé
wrote:
Same problem here:- I'm building FreeBSD head on a builder machine, and NFS
mounti
Hi,
Building on aarch64/14-CURRENT fails with this error on my rpi4.
It failed on incremental build and tried a clean build today.
First failure was on "World build started on Sun May 29 00:25:17 UTC 2022".
This weekend it still fails (I'm building weekly in Jenkins).
10:04:44 ===> tests/sys/kq
Looks like it might be using an old version of
tests/sys/kqueue/libkqueue/common.h, after
https://cgit.freebsd.org/src/commit/?id=c728c56c870abe230e45cee5c477f0d890ebacef
?
Without seeing how the .o files have been compiled, specifically with which -I
flags, it is impossible to see what is goi
On Mon, Jun 06, 2022 at 09:46:21AM +, Filippo Moretti wrote:
>
> Is it now safe to attempt updating current with UFS?SincerelyFilippo
>
Yes.
Kirk committed a fix:
commit bc218d89200faa021def77732f3d9fde4f4dee13
Author: Kirk McKusick
Date: Tue May 31 19:55:54 2022 -0700
Two bug
> Am 06.06.2022 um 11:59 schrieb Ronald Klop :
>
> on my rpi4…..
> 10:04:45
> 10:04:45
> ld: error: undefined symbol: kevent_cmp
>
> Any thoughts? Similar experience?
>
>
Yes, similar experience(~1 week ago) , specially when using NO_CLEAN flag , as
far as I remember..
`got around this
Hi,
Mmm, took another look. I doubt my clean build was clean as "wipe out
workspace" did not work because the Jenkins agent was offline.
The problem might be PEBCAK[1]. :-)
Doing another build with a fresh Jenkins workspace now. Will take 10+ hours to
compile clang for the millionth time.
Ro
> Am 06.06.2022 um 13:42 schrieb Ronald Klop :
>
>
> ….. Will take 10+ hours to compile clang for the millionth time.
>
I also often prefer compiling on target hardware… but to be honest: cross
compiling
on -j(fullspeed)-machines to PXE-boot one slow boards is the only „painless"
workflow.
From: Alexander Motin
Subject: Re: Kernel crashed with "panic: VERIVY(e->lse-mscount != 0) failed"
Date: Sun, 5 Jun 2022 09:33:21 -0400
> Hi,
>
> Please update your system once more. That wrong assertion was removed
> soon after your checkout at e3aa18ad717.
Thanks. After updating latest commi
