Am Mon, 29 May 2017 14:45:16 -0400 Ed Maste <ema...@freebsd.org> schrieb:
> On 29 May 2017 at 04:59, O. Hartmann <ohartm...@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. There is none, so far, it is due to WITH_LLD_IS_LD. 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. Kind regards, oh -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).
pgpsEiv7BjJRF.pgp
Description: OpenPGP digital signature
