On Mon, Nov 19, 2018 at 06:12:39PM +0000, Ed Maste wrote: > Author: emaste > Date: Mon Nov 19 18:12:39 2018 > New Revision: 340640 > URL: https://svnweb.freebsd.org/changeset/base/340640 > > Log: > libc: forcibly disable BIND_NOW > > Building libc WITH_BIND_NOW results in segfault at process start. For > now force BIND_NOW off until the root cause can be identified and fixed. > > PR: 233333 > Sponsored by: The FreeBSD Foundation > > Modified: > head/lib/libc/Makefile > > Modified: head/lib/libc/Makefile > ============================================================================== > --- head/lib/libc/Makefile Mon Nov 19 17:33:44 2018 (r340639) > +++ head/lib/libc/Makefile Mon Nov 19 18:12:39 2018 (r340640) > @@ -6,6 +6,8 @@ SHLIBDIR?= /lib > > .include <src.opts.mk> > > +# BIND_NOW in libc results in segfault at startup (PR 233333) > +MK_BIND_NOW= no
Since the use of ifunc in libc is only applicable to amd64, I wonder if it would be best to disable BIND_NOW in lib/libc/amd64/Makefile.inc. I don't believe there's any need to disable BIND_NOW for libc on other architectures. Thanks, -- Shawn Webb Cofounder and Security Engineer HardenedBSD Tor-ified Signal: +1 443-546-8752 Tor+XMPP+OTR: latt...@is.a.hacker.sx GPG Key ID: 0x6A84658F52456EEE GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE
signature.asc
Description: PGP signature
