From owner-freebsd-current@freebsd.org Tue May 30 16:49:28 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E8B8FB87DA1 for ; Tue, 30 May 2017 16:49:28 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0AF246F03E; Tue, 30 May 2017 16:49:27 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([78.52.137.20]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0LoEPJ-1dql2k2bP7-00gFPC; Tue, 30 May 2017 18:49:19 +0200 Date: Tue, 30 May 2017 18:49:13 +0200 From: "O. Hartmann" To: Ed Maste Cc: "O. Hartmann" , freebsd-current Subject: Re: After ino64 update: devel/libunwind failure: cannot preempt symbol '_Ux86_64_local_addr_space' defined Message-ID: <20170530184849.6e6eafe6@thor.intern.walstatt.dynvpn.de> In-Reply-To: References: <20170529105949.1cecf4e2@freyja.zeit4.iv.bundesimmobilien.de> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/E8KD/6iqO/w/O1UozYGFrRv"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:+7W5fuF6np/7LeGjSPKLcISmVwmWVepDnzXNTFhPHRxqEVJAnXG E6BzIf6hGKboYGluKYMgoJ8caLicH2h3rwPHmouAolhKZntjLLiE7I2C4UpgX868uN7ZQx4 lsVKL50hhz+0IelWdKhV/2Ln2npHxfZsCSMbPiczPrfIC/78atnOTB6GVTZmMkfVYD6cXTr WD5kwsyl6AZkTesrCQSfg== X-UI-Out-Filterresults: notjunk:1;V01:K0:tY4vJSyJhas=:iWEgH5M5bqsmZearWhnh1r Wq4O2wMiUYrVvQJjVBwih266q6BI2VUiEBbQA+KjO81N6SXKH8ht3TBkGYrjTPyrb99TLqXB3 0dZ12sBYexfUMAE+18ioNRVUuU8Lf/4Z8H+HIfVJZ+L1HOb+dmgJa9DWkFXaaxAVO0CT7ivdA k1JYTKTMtccLFkj8Vx2sTUXhmTp64So5/DGNgbRefmMYVtp7pPBbQpQb6syw31ys1jUuxq0wX knuQmWNTjLiAofpodUEF1gUH94tkPMy2KI5C+Bp48bqBcP9rwoBO5e36zj7/gcA73y1PW2X2x MsGkHZ9GoYOf32XOF/lxqe0ApFHNumV+CkIheC+HU3HcObrsAFCFCQL8DviWtBQSv/GwaiUCn c/s80Fm/N82X2c5PgDjfud874N/3rj6i28acvQss17DC0TimeKcmmSRh4i3wgqnuse62n8pOk xUupl8ocvR68exEMP07bd1An8Y1GAlgWepM34wxcysitssQpvMG/DWunBKXOSJHIiJFOxe182 zmoWp/K73S08nm6KH+aQcyQNiVWsqVR9LZRAm+cCLs1YqBkYlusT6lp7uTCTSzTSMX0KB9Mlh 6EczNbQWXQ5M3yHfEbS2/Wi/FCARiyBiIYPHUkGCnHBCIiDTRpNLNA2aXtbsgsFiNj1wD0wYy iivgrGZaT72HodIIOSXYUa+2p1ZTi2LT/2BvJ88cTOUinQ6CtFNRQLLt0sTGbgg6RHkbgexTY 0LzKPFvHlPCfHpNfC2jRypRR/qCSC10+vLfKdUITrMdDzUfguEeZooRBf6o= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 May 2017 16:49:29 -0000 --Sig_/E8KD/6iqO/w/O1UozYGFrRv Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Mon, 29 May 2017 14:45:16 -0400 Ed Maste schrieb: > On 29 May 2017 at 04:59, O. Hartmann wrote: > > After updating several boxes running CURRENT after introduction of ino= 64, 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 Ma= y 28 > > 21:18:52 CEST 2017 amd64, WITH_LLD_IS_LD=3Dyes set. =20 >=20 > 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 wit= h both ino64 AND WITH_LLD_IS_LD, while it failed after an update of a bunch of systems t= owards ino64. Kind regards, oh --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/E8KD/6iqO/w/O1UozYGFrRv Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWS2iiQAKCRDS528fyFhY lPQVAf0eN6EfkNuWDJzFowY7UcfhUdrzICItPtYQcF92wAG7aWFHFeEW8sVkNuNS 7sxiac3wNmaBckUx9b8vgO9RsrmFAf0eOAUNYPtvMDodpHfMrRTTmrBqHZqAA7Kr Socd63k9TWSJ99l/k3O/OYw4fYdOADGDgvxs6CuBnGKURCWaY2wC =H3Dn -----END PGP SIGNATURE----- --Sig_/E8KD/6iqO/w/O1UozYGFrRv--