Received: from mail.shiz.me (immunity.shiz.me [62.210.12.63]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 299DD781F6B for <~alpine/devel@lists.alpinelinux.org>; Fri, 3 Apr 2020 13:32:24 +0000 (UTC) Received: from antimonium.lan (5070ACB7.static.ziggozakelijk.nl [80.112.172.183]) by mail.shiz.me (OpenSMTPD) with ESMTPSA id 5b075c41 (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO); Fri, 3 Apr 2020 13:32:18 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\)) Subject: Re: rust triples (WAS: Re: Planning for 3.12 feature freeze) From: Shiz X-Priority: 3 (Normal) In-Reply-To: Date: Fri, 3 Apr 2020 15:32:18 +0200 Cc: Natanael Copa , Rasmus Thomsen , "~alpine/devel@lists.alpinelinux.org" <~alpine/devel@lists.alpinelinux.org> Content-Transfer-Encoding: quoted-printable Message-Id: <280DD35B-697F-41E2-89E7-7235690B8DD4@shiz.me> References: To: Jean-Louis Fuchs X-Mailer: Apple Mail (2.3601.0.10) > On Apr 3, 2 Reiwa, at 14:09, Jean-Louis Fuchs = wrote: >=20 > So my point is $arch-alpine-linux-musl feels correct. BUT could we = just > introduce $arch-unknown-linux-dynmusl? Because if we patch crt-static = away > on a rust-build using $arch-unknown-linux-musl, we might break things = that > expect crt-static. I think this is a worse solution than making $arch-alpine-linux-musl = dynamically linked, as the author fo said patch, and expect it to break more things than an = -alpine- triple would. > Either way it was a very bad idea to link crt-static with the triplet. +1, but that=E2=80=99s sadly how it is for the upstream. I propose we = move to $arch-alpine-linux-musl everywhere and fix any outstanding issues with it. I can help if needed. - Shiz