From owner-freebsd-current@freebsd.org Tue May 30 20:41:52 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 F0F86BED152 for ; Tue, 30 May 2017 20:41:52 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B8A677910D for ; Tue, 30 May 2017 20:41:52 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-it0-x231.google.com with SMTP id w68so11764548itc.0 for ; Tue, 30 May 2017 13:41:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=OrLKOB+1O2mfUtABYMaxId6LpRoybcgzmwYZIg3K19I=; b=MIJvX7FHovf3U+3Ne6lO5PdhNxzBH+NkcGBK2sTeAXJynRFgCpuXgTWx1LleHMVhK5 T4XceuCyxZC04RpBQ4Xh/SAMNwOs4P9/ZaOzcdluYtO3r5V0YBeKT/NTq0Dr4PdLWU0d gEJoyuLaacrpmOFGNL2DBdVzB7+oNXO8vafuVS+Lrmtop1Nim5hYR5epBS4v6iMvew65 S9BxnT76xfsgUX6E+N3/TLMEeys9dFrLw6DuH9xZUCbkFylJ5Yhc19E/OPGGxyIsAhno dqrpbEWwaiu/fEHKcH8ncncfESRTlx5NY6z3ZwVYfevawhGkYcgqDfct+eRLArb72TRl PKbA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=OrLKOB+1O2mfUtABYMaxId6LpRoybcgzmwYZIg3K19I=; b=VRB2cOBj3BtlIjlIhs5CrzXOEqjCGRjiMsoKE+xR5+agd1ituK5w8RZ0jij3HJihex /OX/X4pAftDpzqfXmOo/mkM8ZvMWbomcNWA3Q+etxpyaQVIK1SZs+cyymjYUSTE4oaVz LldGg9e9Jtdw8kE/uaZuJCIF7SfuYPZOhqJWVEessD4imdNiN6hVicpeKvDPNghopRuy NtAwjRcYgMd/Cc0qdu4HqfcGJ4YObaJrjbovXhpS/jF3LZq/jnxKpFnmxkFovWfL3lZX CNfcA/hgvbPmwTSBq5NiK22yZHxqSACJ1uDA+BKqXh/3JWcywVFDU/MPh0ITNUoYaBIV cXOA== X-Gm-Message-State: AODbwcALgUPgnGgS+VxZ8tXE5U9lumhuRsZNEtDnnCkm3Nkgf4aN4bvu fQl7/3evafivPQW7uCm4CX1pXV2GvuW/ X-Received: by 10.36.43.146 with SMTP id h140mr3896949ita.7.1496176911981; Tue, 30 May 2017 13:41:51 -0700 (PDT) MIME-Version: 1.0 Sender: carpeddiem@gmail.com Received: by 10.107.169.201 with HTTP; Tue, 30 May 2017 13:41:31 -0700 (PDT) In-Reply-To: <20170530184849.6e6eafe6@thor.intern.walstatt.dynvpn.de> References: <20170529105949.1cecf4e2@freyja.zeit4.iv.bundesimmobilien.de> <20170530184849.6e6eafe6@thor.intern.walstatt.dynvpn.de> From: Ed Maste Date: Tue, 30 May 2017 16:41:31 -0400 X-Google-Sender-Auth: 5VmBLnK4q22UCSweDj02cvGENV0 Message-ID: Subject: Re: After ino64 update: devel/libunwind failure: cannot preempt symbol '_Ux86_64_local_addr_space' defined To: "O. Hartmann" Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" 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 20:41:53 -0000 On 30 May 2017 at 12:49, O. Hartmann 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.