From nobody Wed Nov 17 21:44:46 2021 X-Original-To: freebsd-current@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 B1C1718963BD for ; Wed, 17 Nov 2021 21:44:50 +0000 (UTC) (envelope-from se@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Hvc0L4Lfwz4bgD; Wed, 17 Nov 2021 21:44:50 +0000 (UTC) (envelope-from se@freebsd.org) Received: from [IPV6:2003:cd:5f2e:2500:fc45:3285:e123:4572] (p200300cd5f2e2500fc453285e1234572.dip0.t-ipconnect.de [IPv6:2003:cd:5f2e:2500:fc45:3285:e123:4572]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: se/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id B7710FFDC; Wed, 17 Nov 2021 21:44:49 +0000 (UTC) (envelope-from se@freebsd.org) Message-ID: <51a2d269-53c3-4bee-a69d-86b36f436e04@freebsd.org> Date: Wed, 17 Nov 2021 22:44:46 +0100 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.3.0 Subject: Re: Incompatible change in LLD13 causing link errors? Content-Language: en-US To: Dimitry Andric , acm@FreeBSD.org Cc: FreeBSD CURRENT , Jessica Clarke References: From: Stefan Esser In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------0h4060H0KBJoJCwmMgzYqH8n" X-ThisMailContainsUnwantedMimeParts: N This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------0h4060H0KBJoJCwmMgzYqH8n Content-Type: multipart/mixed; boundary="------------wrCLEdGwalYcgERdjhKakvxF"; protected-headers="v1" From: Stefan Esser To: Dimitry Andric , acm@FreeBSD.org Cc: FreeBSD CURRENT , Jessica Clarke Message-ID: <51a2d269-53c3-4bee-a69d-86b36f436e04@freebsd.org> Subject: Re: Incompatible change in LLD13 causing link errors? References: In-Reply-To: --------------wrCLEdGwalYcgERdjhKakvxF Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am 17.11.21 um 21:20 schrieb Dimitry Andric: > On 17 Nov 2021, at 21:07, Stefan Esser wrote: >> >> I have just received pkg-fallout for a port that has not been touched >> for several months, specifically lang/silq. >> >> ld.lld: error: undefined hidden symbol: __start___minfo >>>>> referenced by terminal.d >>>>> silq.o:(ldc.register_dso) >> >> ld.lld: error: undefined hidden symbol: __stop___minfo >>>>> referenced by terminal.d >>>>> silq.o:(ldc.register_dso) >> cc: error: linker command failed with exit code 1 (use -v to see invoc= ation) >> Error: /usr/bin/cc failed with status: 1 >> *** Error code 1 >> >> This port builds correctly with LLD12 from a port, but fails with the >> error message included above for both LLD13 from a port and LLD from >> the FreeBSD-CURRENT base system. >=20 > See https://bugs.llvm.org/show_bug.cgi?id=3D52384 where this is discuss= ed. > Executive summary is to add -Wl,-z,nostart-stop-gc to your LDFLAGS, for= > now at least. But as you can see in the upstream PR, not everybody is > happy with them flipping the default to on. Hi Dimitry, thank you for the quick reply! Seems that the breakage of LDC had been noticed (by Jessica?) a few weeks ago, and that a possible solution could be to build LDC with LLVM>=3D13.0.0. But apparently LDC-1.23.0 cannot be built with llvm13, and a naive attempt to upgrade the LDC port to 1.28.0 failed (MAINTAINER in CC). Since LDC currently depends on LLVM10 I'll just add that as a dependency to my failing port and hard-code lld10 as the linker to use. A better fix could be to import the (apparently not yet completely accepted) patch https://github.com/ldc-developers/ldc/pull/3850/ to explicitly define the garbage collected symbols in rt.dso into LDC. Anyway, my lang/silq port seems to be fixed by using llvm10 (poudriere test builds ongoing). Regards, STefan --------------wrCLEdGwalYcgERdjhKakvxF-- --------------0h4060H0KBJoJCwmMgzYqH8n Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsB5BAABCAAjFiEEo3HqZZwL7MgrcVMTR+u171r99UQFAmGVd84FAwAAAAAACgkQR+u171r99USv Ogf9GIibyq+in4WG+GEgjfrphhQF2vBs2EynuiZnjIIc9I7rUrvkFWTd2/zG1ES/X/0oXO+t3Cn8 RFq4BWmOiHmGxsrwx5j5/QKoDx/D1PxuxkDEZq3h2usAlPI0CqDEojKl1eXn/HjQ2b5pxuFVK8gH kkSi5z008/dkjScWWzxuM5f8Pel7kPkHnvv6jegb7/cXy4PN+ufQdL5BOqTMOswcz7ZCvD2fQQKn CbSTPr9fZfMe2x9O5+UlDLTbKRJUqUZ9d5GFb3LHmZUsY/1343i3DRg78SUOXCD+GoxtEVVLnRIQ Eti5SDygIzi/EQUKziXiVtu/eFDMHgTW6UAT2guUpQ== =bYnJ -----END PGP SIGNATURE----- --------------0h4060H0KBJoJCwmMgzYqH8n--