From nobody Fri Nov 26 09:21:54 2021 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 63B2118AB52C for ; Fri, 26 Nov 2021 09:22:08 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (mx1.sbone.de [IPv6:2a01:4f8:13b:39f::9f:25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4J0q5D1fjsz3Kpf for ; Fri, 26 Nov 2021 09:22:08 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id EC0308D4A129; Fri, 26 Nov 2021 09:21:57 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 20C59E70815; Fri, 26 Nov 2021 09:21:57 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id XCKXVXthCBIa; Fri, 26 Nov 2021 09:21:55 +0000 (UTC) Received: from [169.254.1.48] (unknown [IPv6:fde9:577b:c1a9:4902:2cb2:a87c:b0d6:7458]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id A894AE707D9; Fri, 26 Nov 2021 09:21:55 +0000 (UTC) From: "Bjoern A. Zeeb" To: greg@unrelenting.technology Cc: freebsd-arm@freebsd.org Subject: Re: world linker error "can't create dynamic relocation R_AARCH64_LDST64_ABS_LO12_NC against symbol: __stderrp in readonly segment" Date: Fri, 26 Nov 2021 09:21:54 +0000 X-Mailer: MailMate (2.0BETAr6151) Message-ID: <4C688B42-E443-4B44-9048-7B84BCE35982@lists.zabbadoz.net> In-Reply-To: <5B9D4DF1-32FE-4918-9A8F-DF528E88BD05@unrelenting.technology> References: <5B9D4DF1-32FE-4918-9A8F-DF528E88BD05@unrelenting.technology> List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4J0q5D1fjsz3Kpf X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On 25 Nov 2021, at 23:53, Greg V via freebsd-arm wrote: >> On 25 Nov 2021, at 04:38, Bjoern A. Zeeb = >> wrote: >> >> =EF=BB=BFHi, >> >> I am trying to update one machine (also across the LLVM update) and I = >> get the below error. >> Anyone any ideas? >> >> >> ld: error: relocation R_AARCH64_ADR_PREL_PG_HI21 cannot be used = >> against symbol __stderrp; recompile with -fPIC >>>>> defined in = >>>>> base14-251054.3ede04c78c7c726ed79a39d22c65a58d0ecc5d00/arm64.aarch6= 4/tmp/lib/libc.so.7 >>>>> referenced by assert.c >>>>> assert.o:(libspl_assertf) in archive = >>>>> base14-251054.3ede04c78c7c726ed79a39d22c65a58d0ecc5d00/arm64.aarch6= 4/tmp/usr/lib/libspl.a > > That would be https://reviews.freebsd.org/D32521#739094 =E2=80=93 this = was = > fixed in the final version of the patch that actually was committed = > though. > > And I=E2=80=99ve just checked that it all builds on aarch64 too. Works = for = > me, and presumably for anyone else building world in the last 10 days = > or so. So that=E2=80=99s weird. Maybe some leftover /usr/obj state some= how = > causing issues or something? We found that this particular build issue is caused by WITH_CDDL and = WITHOUT_ZFS as a result of a recent commit to fix library dependencies = in that area; markj has given me a patch and I tested it successfully = for that specific case last night at almost 2AM; I assume the issue = will be solved the next days in main. Sorry for not following up = anymore last night right away. /bz