On Wed, 21 Feb 2018 20:01+0100, Ronald Klop wrote: > On Tue, 20 Feb 2018 11:30:52 +0100, Trond Endrestøl > <trond.endres...@fagskolen.gjovik.no> wrote: > > > On Mon, 19 Feb 2018 23:38+0100, Ronald Klop wrote: > > > > > Does this mean I always have to do a *clean* buildworld after every > > > version > > > bump? This takes ages. > > > > Yes, I've come to the conclusion that whenever __FreeBSD_version in > > sys/sys/param.h is incremented, then it's time to blow away /usr/obj, > > recreate everything to ensure the correct value of osversion in the > > .note.tag section of each executable, and reinstall base prior to > > updating localbase. See PR 225104 for more details, > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225104. > > > > pkg: Newer FreeBSD version for package gnome-menus: > - package: 1200058 > - running kernel: 1200056 > > So it says "running kernel", but it actually checked "version of > FreeBSD_version while building /bin/sh" or something like that. > This sounds over-engineered and (more important) confusing.
I tried the simply approach of running "make clean; make build" in /usr/src/bin/sh, hoping it would generate binaries with the correct osversion in the .note.tag section. Boy, I couldn't be more wrong. Hence my (possibly wrongful) conclusion of wiping /usr/obj whenever osversion is increased. I'm probably missing a simpler step. -- Trond. _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
