Received: from srsyg17.sygroup-int.ch (srsyg17.sygroup-int.ch [95.128.32.155]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 2FBE9782B24 for <~alpine/devel@lists.alpinelinux.org>; Fri, 3 Apr 2020 12:09:38 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by srsyg17.sygroup-int.ch (Postfix) with ESMTP id 8841A2A039; Fri, 3 Apr 2020 14:09:37 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at srsyg17.sygroup-int.ch Received: from srsyg17.sygroup-int.ch ([127.0.0.1]) by localhost (srsyg17.sygroup-int.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 3LI4YqsWA6xZ; Fri, 3 Apr 2020 14:09:37 +0200 (CEST) Received: from srsyg17.sygroup-int.ch (localhost [IPv6:::1]) by srsyg17.sygroup-int.ch (Postfix) with ESMTP id 56B222A002; Fri, 3 Apr 2020 14:09:37 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=adfinis-sygroup.ch; s=mail; t=1585915777; bh=O72BwWE9+3UOTkP0t8xgQlO993gmf7TlBJ9T8ar2NPk=; h=Subject:From:To:Cc:Date; b=s1fyJjks90Z5t+/089+7ZSa68xK/Wrri0eiDhh6yQlI43HzdH9667Xzf9jCzUV7mc RcQ8aF1yyjL6VcYi5QQygAYcpy7/7MK5o6LOx8oA4Yj42xjvK0jkiSceuvP78xHr4z 36DnNWjiPoOOSONCox82s6IgEdEQx6UT1aWs3FVI= Received: by srsyg17 (kopano-spooler) with MAPI; Fri, 3 Apr 2020 14:09:37 +0200 Subject: RE: rust triples (WAS: Re: Planning for 3.12 feature freeze) From: "Jean-Louis Fuchs" To: "Natanael Copa" , "Rasmus Thomsen" Cc: =?us-ascii?Q?=7Ealpine/devel=40lists=2Ealpinelinux=2Eorg?= <~alpine/devel@lists.alpinelinux.org> Date: Fri, 3 Apr 2020 12:09:37 +0000 Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-Mailer: Kopano 8.7.9 Message-Id: Hi > > Ok. I still think we should either use `*-unknown-linux` or `*-alpine-linux` > consistenly only all arches. > > I don't know which is to prefer though. > > https://gitlab.alpinelinux.org/alpine/aports/issues/11349 > > -nc > My 50 cents. I run x86_64-unknown-linux-musl from rustup. I still have RUSTFLAGS=3D"-C target-feature=3D-crt-static" set. Packages like rocket (web framework) and diesel (ORM) work, I haven't tried compiling firefox, though. It was planned to create a triplet $arch-unknown-linux-dynmusl which is meant for hosts running musl. [1] This hasn't happened yet and instead many bugs have been fixed so $arch-unknown-linux-musl works as host and not only as a target. It was said, that they never remove the requirement for -crt-static, because it will break a lot of build-systems out there, that think $arch-unknown-linux-musl is only a target for creating static binaries. [1] https://github.com/rust-lang/rust/issues/59302 So my point is $arch-alpine-linux-musl feels correct. BUT could we just introduce $arch-unknown-linux-dynmusl=3F Because if we patch crt-static away on a rust-build using $arch-unknown-linux-musl, we might break things that expect crt-static. If packages only look at the middle part *-unknown-linux-* it might fix most problems. Either way it was a very bad idea to link crt-static with the triplet. Let me know if you think creating $arch-unknown-linux-dynmusl rust-build is worth a try=3F Best, Jean-Louis