Date: Tue, 30 May 2017 16:41:31 -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: <CAPyFy2AiQ33HmffZQb4UBdvPstxzOKeYYdYr33AVax6yfuP8eA@mail.gmail.com> In-Reply-To: <20170530184849.6e6eafe6@thor.intern.walstatt.dynvpn.de> References: <20170529105949.1cecf4e2@freyja.zeit4.iv.bundesimmobilien.de> <CAPyFy2Bt-bM-2v2S_wM655-5SMUQdUfrz7EwiELRJrgAxgWtWQ@mail.gmail.com> <20170530184849.6e6eafe6@thor.intern.walstatt.dynvpn.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 30 May 2017 at 12:49, O. Hartmann <ohartmann@walstatt.org> wrote: > > I got a kind of confused, since libunwind seemingly compiles on one box with both ino64 > AND WITH_LLD_IS_LD, while it failed after an update of a bunch of systems towards ino64. So was this just confusion over what was actually built? I believe libunwind should always fail with LLD.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2AiQ33HmffZQb4UBdvPstxzOKeYYdYr33AVax6yfuP8eA>