HEADSUP: Something has gone south with -current
kostikbel at gmail.com
Sat Dec 8 00:08:32 UTC 2018
On Fri, Dec 07, 2018 at 03:52:33PM -0800, Steve Kargl wrote:
> On Fri, Dec 07, 2018 at 03:30:19PM -0800, Steve Kargl wrote:
> > On Fri, Dec 07, 2018 at 03:06:22PM -0800, Steve Kargl wrote:
> > >
> > > make core dumps.
> > > devd core dumps.
> > > init core dumps.
> > > cc core dumps.
> > > c++ core dumps.
> > >
> > > Something seems to be broken.
> > >
> > Further investigation,
> > as core dumps.
> > cpp core dumps.
> > /rescue/vi core dumps.
> > All of these programs are statically linked. Note, ar and ranlib
> > have static linkage, and appear to still work but these were not
> > replaced by the failing 'make installworld'.
> > Ah, so if I go into /usr/obj/usr/src/amd64.amd64/ar, this ar
> > is static and not stripped and works! But, if I do
> > cp ar ar.new
> > strip ar
> > ./ar
> > This ar core dumps. So, stripping static binaries seems to
> > break the binary.
> Yep, definitely, a problem with stripping static binaries.
> I copied both init and devd from /usr/obj to /sbin without
> stripping the binaries. System rebooted as expected.
Most likely this is an issue fixed by r339350.
More information about the freebsd-current