[Bug 275482] ports-mgmt/pkg: incorrectly complains about outdated os version

From: <bugzilla-noreply_at_freebsd.org>
Date: Fri, 16 Feb 2024 07:45:34 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275482

--- Comment #17 from Martin Birgmeier <d8zNeCFG@aon.at> ---
Checking sys/sys/param.h reveals that it was last changed on Feb. 9.

[0]% cd /usr/src
[0]% ll sys/sys/param.h 
-rw-r--r--  1 src srcs 13577 Feb  9 12:03 sys/sys/param.h
[0]% git log sys/sys/param.h | head -8
commit b566e44b2b88eb9f1b3b658998c7418cccab9e2f
Author: Konstantin Belousov <kib@FreeBSD.org>
Date:   Wed Jan 31 02:47:49 2024 +0200

    stable/14: bump __FreeBSD_version for kcmp(2) and kern_openatfp(9)

    Sponsored by:   The FreeBSD Foundation

[0]% 

On Feb. 14 I did the cherry-pick:

[0]% fc -liD 1 | grep cherry-pick      
 4986  2024-02-14 07:44  0:37  git cherry-pick
ed3563b0ac31d854bf907d4d847ac0195ec9637b
[0]% 

And I started the -DNO_CLEAN buildworld buildkernel later (I am keeping
logfiles whose name contains the start time):

[0]# ll
/usr/obj/usr/src/make.-j16.-DNO_CLEAN.buildworld.buildkernel.KERNCONF=XYZZY_SMP.XYZZY_SMP_VM.GENERIC.2024-02-14.19:07:32@v904
-rw-r--r--  1 root srcs 37319862 Feb 14 19:50
/usr/obj/usr/src/make.-j16.-DNO_CLEAN.buildworld.buildkernel.KERNCONF=XYZZY_SMP.XYZZY_SMP_VM.GENERIC.2024-02-14.19:07:32@v904
[0]# 

And crtbrand.o really was rebuilt:

[0]% ll /usr/obj/usr/src/amd64.amd64/lib/csu/amd64 
total 39
-rw-r--r--  1 root srcs 2280 Feb 14 19:11 Scrt1.o
-rw-r--r--  1 root srcs  960 Nov 11 17:41 Scrt1_c.o
-rw-r--r--  1 root srcs 2288 Feb 14 19:11 crt1.o
-rw-r--r--  1 root srcs 1160 Nov 11 17:41 crt1_c.o
-rw-r--r--  1 root srcs  968 Nov 11 17:41 crt1_s.o
-rw-r--r--  1 root srcs 2304 Feb  9 17:18 crtbegin.o
-rw-r--r--  1 root srcs 2560 Feb  9 17:18 crtbeginS.o
-rw-r--r--  1 root srcs 2304 Feb  9 17:18 crtbeginT.o
-rw-r--r--  1 root srcs  664 Feb 14 19:11 crtbrand.o
-rw-r--r--  1 root srcs 1720 Nov 11 17:41 crtend.o
-rw-r--r--  1 root srcs 1720 Nov 11 17:41 crtendS.o
-rw-r--r--  1 root srcs 1072 Feb 14 19:11 crti.o
-rw-r--r--  1 root srcs  656 Nov 11 17:41 crti_s.o
-rw-r--r--  1 root srcs  600 Nov 11 17:41 crtn.o
-rw-r--r--  1 root srcs  552 Nov 11 17:41 feature_note.o
-rw-r--r--  1 root srcs 2432 Feb 14 19:11 gcrt1.o
-rw-r--r--  1 root srcs 1104 Nov 11 17:41 gcrt1_c.o
-rw-r--r--  1 root srcs  552 Nov 11 17:41 ignore_init_note.o
[0]% 

But uname was not:

[0]% ll /usr/obj/usr/src/amd64.amd64/usr.bin/uname 
total 24
-rwxr-xr-x  1 root srcs 17464 Feb  9 17:48 uname
-rw-r--r--  1 root srcs  2015 Nov 11 18:01 uname.1.gz
-rw-r--r--  1 root srcs 23192 Feb  9 17:48 uname.o
[0]% 

So the events were
- sys/sys/param.h update on Feb 9
- cherry-pick on Feb 14
- build -DNO_CLEAN on Feb 14

And the result was that crtbrand.o was indeed rebuilt, but not uname.

Would uname be rebuilt if I touched param.h again?

-- Martin

-- 
You are receiving this mail because:
You are the assignee for the bug.