Re: ino64? r318606 -> r318739 OK; r318739 -> r318781 fails SIGSEGV

From: Dimitry Andric <dim_at_FreeBSD.org>
Date: Wed, 24 May 2017 14:10:08 +0200
On 24 May 2017, at 13:59, David Wolfskill <david_at_catwhisker.org> wrote:
> 
> Yesterday's in-place src update (r318606 -> r318739) was a bit more
> "interesting" than usual; as has been noted elsewhere, it really is
> necessary to boot the new kernel before the "make installworld"
> completes successfully.  That said, it ("make installworld") did
> complete successfully, and a followup reboot/smoke test worked without
> incident.
> 
> For today's update, sources are now at r318781; both laptop and build
> machine fail identically during ">>> stage 4.2: building libraries":
> 
> ...
> Building /common/S4/obj/usr/src/lib/libc/strsignal.pico
> Building /common/S4/obj/usr/src/lib/libc/libc.a
> --- libc.a ---
> building static c library
> Building /common/S4/obj/usr/src/lib/libc/libc.so.7
> Building /common/S4/obj/usr/src/lib/libc/libc_pic.a
> --- libc.so.7 ---
> building shared library libc.so.7
> --- libc_pic.a ---
> building special pic c library
> --- libc.so.7 ---
> cc: error: unable to execute command: Segmentation fault (core dumped)
> cc: error: linker command failed due to signal (use -v to see invocation)
> *** [libc.so.7] Error code 254

Looks like your linker is crashing.  Can you figure out:
1) The exact linker command being run
2) The path to the linker executable that crashes
3) Backtrace of the crash

-Dimitry


Received on Wed May 24 2017 - 10:10:27 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:11 UTC