Date: Mon, 29 May 2017 14:45:16 -0400 From: Ed Maste <emaste@freebsd.org> To: "O. Hartmann" <ohartmann@walstatt.org> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: After ino64 update: devel/libunwind failure: cannot preempt symbol '_Ux86_64_local_addr_space' defined Message-ID: <CAPyFy2Bt-bM-2v2S_wM655-5SMUQdUfrz7EwiELRJrgAxgWtWQ@mail.gmail.com> In-Reply-To: <20170529105949.1cecf4e2@freyja.zeit4.iv.bundesimmobilien.de> References: <20170529105949.1cecf4e2@freyja.zeit4.iv.bundesimmobilien.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 29 May 2017 at 04:59, O. Hartmann <ohartmann@walstatt.org> wrote: > After updating several boxes running CURRENT after introduction of ino64, I > have one box which persitently rejects compiling and installing > devel/libunwind, as you can finde below. > > The box in question is running FreeBSD 12.0-CURRENT #22 r319083: Sun May 28 > 21:18:52 CEST 2017 amd64, WITH_LLD_IS_LD=yes set. What's the difference between this and the report in PR 219524? AFAICT this is just a known issue with the libunwind port and LLD, and will need a change in libunwind to fix.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2Bt-bM-2v2S_wM655-5SMUQdUfrz7EwiELRJrgAxgWtWQ>