Date: Tue, 09 Jul 2019 19:35:16 +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-QzMP34Y46B@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 #46 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Justin Hibbits from comment #45) Okay. Note that beyond eliminating such from what -lc++ pulled in (coment #32 that I fogot to mention), I had to eliminate such from ports (comment #38 that I mentioned): For sure: devel/libedit textproc/libxml2 converters/libiconv Possibly: math/gmp math/mpfr math/mpc I'm not aware of __bss_start in the .dynsym information being anywhere else impacting my tests. I've not seen the problem again in any context after rebuilding everything (system and ports) to not have __bss_start in the .dynsym information. But I did have to rebuild everything involved by using a toolchain that did not add __bss_start in the .dynsym information, including in poudriere so that the ports involved would avoid such as well. If there is another way for the problem to happen, isolating it may be easier from an environment that does not have any examples involved with __bss_start in the .dynsym information . Unfortunately I've no clue how to cause the problem in such a context. --=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-QzMP34Y46B>