On Fri, Dec 07, 2018 at 05:02:03PM -0800, Steve Kargl wrote: > On Sat, Dec 08, 2018 at 02:43:17AM +0200, Konstantin Belousov wrote: > > On Fri, Dec 07, 2018 at 04:25:39PM -0800, Steve Kargl wrote: > > > On Sat, Dec 08, 2018 at 02:08:20AM +0200, Konstantin Belousov wrote: > > > > > > > > Most likely this is an issue fixed by r339350. > > > > > > My tree is at r341703. The last paragraph of the commit > > > message for r339350 is > > Which tree ? The strip that is used by install should be past this > > revision. > > > This is the /usr/src that has led to the broken static binaries. > > Looking at timestamps, I have > > % ls -l /usr/bin/strip > -r-xr-xr-x 2 root wheel - 131144 Oct 10 17:10 /usr/bin/strip* > > which is the strip from my Oct 10 build. This strip did not get > updated because 'make installworld' died. Does install during > an installworld use the old strip instead of freshly built strip? >
Looks like /usr/src/UPDATING could use an entry about r339350. I was updating an r339290 world to r341703. This jumps across r339350. /usr/bin/strip from r339290 apparently is used during installworld, which renders a system rather broken. 20181013: At r339350, /usr/bin/strip was updated to deal with the introduction of ifuncs into FreeBSD. In particular, a /usr/bin/strip from an earlier revision can lead to a broken system. To avoid mayhem, it is suggested that one does cd /usr/src/usr.bin/objcopy make install prior to 'make installworld' -- Steve _______________________________________________ firstname.lastname@example.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"