From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56891) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e98MQ-0002up-Gm for guix-patches@gnu.org; Mon, 30 Oct 2017 07:36:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e98MM-0008P8-J1 for guix-patches@gnu.org; Mon, 30 Oct 2017 07:36:06 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:60955) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1e98MM-0008Ox-G0 for guix-patches@gnu.org; Mon, 30 Oct 2017 07:36:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1e98MM-0001I2-3p for guix-patches@gnu.org; Mon, 30 Oct 2017 07:36:02 -0400 Subject: [bug#28433] [WIP] Rust update Resent-Message-ID: Date: Mon, 30 Oct 2017 12:35:01 +0100 From: Danny Milosavljevic Message-ID: <20171030123501.66cebab2@scratchpost.org> In-Reply-To: <87d1575dsw.fsf@gnu.org> References: <20170912185023.7de883ff@scratchpost.org> <873767cnsu.fsf@elephly.net> <20171026101728.6493ef46@scratchpost.org> <20171028124258.22553eee@scratchpost.org> <20171028133157.4dc52bd9@scratchpost.org> <20171028135726.76e5a14e@scratchpost.org> <87d1575dsw.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: Ricardo Wurmus , 28433@debbugs.gnu.org On Sat, 28 Oct 2017 20:26:39 +0200 ludo@gnu.org (Ludovic Court=C3=A8s) wrote: > Danny Milosavljevic skribis: >=20 > > Do we support lib32 a la "gcc -m32" ? How can we provide a working glib= c for that? It seems that rustc bootstrap is trying to use that option. =20 >=20 > We don=E2=80=99t support multilib, so glibc provides only 64-bit headers = on > x86_64 (if you try -m32 there you=E2=80=99ll get an error about missing > or something like that.) Yeah. What happens when I use an i686 host/target gcc and use "-m32" (rustbuild d= oes that)? Will it just ignore the option?