Date: Tue, 09 Jul 2019 17:57:56 +0000 From: bugzilla-noreply@freebsd.org To: toolchain@FreeBSD.org Subject: [Bug 237068] /usr/local/bin/ld: BFD (GNU Binutils) 2.30 assertion fail elflink.c:2824 Message-ID: <bug-237068-29464-cPgJWRgpz4@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-237068-29464@https.bugs.freebsd.org/bugzilla/> References: <bug-237068-29464@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237068 --- Comment #44 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Justin Hibbits from comment #43) In your environment, does the find command from comment #42 show the __bss_start in the .dynsym information in anything involved in the link? Vs.: have you gotten the message without that being involved? Comment #38 listed where I eliminated such __bss_start information in order to have llvm60 and llvm80 build. That should at least be a start at what to look for having .dynsym information. As far as I can tell, having __bss_start in the .dynsym information for the link is sufficient to have the problem. But it might not be the only way to have it. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-237068-29464-cPgJWRgpz4>