unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Adam Van Ymeren <adam@vany.ca>
Cc: guix-devel@gnu.org
Subject: Re: Rust bootstraps via i686?
Date: Tue, 5 Dec 2017 12:36:02 +0200	[thread overview]
Message-ID: <20171205103602.GE19582@macbook41> (raw)
In-Reply-To: <874lp6xo5k.fsf@vany.ca>

[-- Attachment #1: Type: text/plain, Size: 1009 bytes --]

On Mon, Dec 04, 2017 at 02:56:39PM -0500, Adam Van Ymeren wrote:
> Does anyone know why rust bootstraps itself from the i686 version of the
> binaries even if you're running on x86_64?
> 
> This results in having to download a build a lot of packages to build
> rust on x86_64.
> 
> If I can make it bootstrap though the current system in use would that
> be a useful patch or is there some problem with bootstraping from x86_64
> that I'm unaware of?
> 
> Thanks!
> -Adam
> 

I believe the reason is to decrease the number of language-specific
bootstrap binaries. Since the i686 bootstrap rust is capable of building
for i686 and for x86_64, it means one less binary.

On the other hand, this does nothing for the other architectures which
can't execute i686 code natively.

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-12-05 10:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-04 19:56 Rust bootstraps via i686? Adam Van Ymeren
2017-12-05 10:36 ` Efraim Flashner [this message]
2017-12-05 13:11   ` ng0
2017-12-06  8:40 ` Danny Milosavljevic

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171205103602.GE19582@macbook41 \
    --to=efraim@flashner.co.il \
    --cc=adam@vany.ca \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).