UPDATING: Not unusual side effect of the awk bug fixed in d4d252c499
You might not be able to build the kernel if you have an awk between Jul 7th and today. It does not affect all platforms due to the nature of the bug (so amd64 is unaffected in stable/13 or current, but is affected in stable/12. i386 seems to be affected everywhere). Sponsored by: Netflix
This commit is contained in:
parent
d4d252c499
commit
5ede4fc06d
12
UPDATING
12
UPDATING
@ -27,6 +27,18 @@ NOTE TO PEOPLE WHO THINK THAT FreeBSD 14.x IS SLOW:
|
||||
world, or to merely disable the most expensive debugging functionality
|
||||
at runtime, run "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
|
||||
|
||||
20210715:
|
||||
The 20210707 awk update brought in a change in behavior. This has
|
||||
been corrected as of d4d252c49976. Between these dates, if you
|
||||
installed a new awk binary, you may not be able to build a new
|
||||
kernel because the change in behavior affected the genoffset
|
||||
script used to build the kernel. If you did update, the fix is
|
||||
to update your sources past the above hash and do
|
||||
% cd usr.bin/awk
|
||||
% make clean all
|
||||
% sudo -E make install
|
||||
to enable building kernels again.
|
||||
|
||||
20210708:
|
||||
Commit 1e0a518d6548 changed the internal KAPI between the NFS
|
||||
modules. They all need to be rebuilt from sources. I did not
|
||||
|
Loading…
Reference in New Issue
Block a user