Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rustup installs i686 versions on 64-bit Windows #296

Closed
White-Oak opened this issue Apr 11, 2016 · 5 comments
Closed

Rustup installs i686 versions on 64-bit Windows #296

White-Oak opened this issue Apr 11, 2016 · 5 comments

Comments

@White-Oak
Copy link

I had to manually specify x86_64-pc-windows-gnu triple to get 64-bit version.
Is it intended?

@White-Oak White-Oak changed the title Rustup default nightly install i686 version on 64-bit Windows Rustup installs i686 versions on 64-bit Windows Apr 11, 2016
@nodakai
Copy link
Contributor

nodakai commented Apr 11, 2016

It appears that win.rustup.rs is (sort of) an alias to
https://static.rust-lang.org/rustup/dist/i686-pc-windows-gnu/rustup-setup.exe
(32 bit Mingw build)

@brson
Copy link
Contributor

brson commented Apr 13, 2016

This is intended, for two reasons: 1) I'd much rather have users download a single program than have to pick between 32-bit and 64-bit builds (or worse - between 32/64/gnu/msvc), 2) There's no particular reason to tie the default architecture to the architecture of the download.

Right now you can switch to a 64-bit toolchains by installing them explicitly, like rustup default nightly-x86_64-pc-windows-gnu.

I suspect that my preferred ultimate solution will be to have a configuration option for default host. At install time (perhaps just on windows), we'll mention "oh, and this is the target you'll build for by default", and then it can be changed interactively (or via command line switch).

@brson
Copy link
Contributor

brson commented Apr 13, 2016

In the meantime, if you really need a build that defaults to 64-bit you can still download it from the "other installation methods" section of the README.

@brson
Copy link
Contributor

brson commented Apr 13, 2016

@brson
Copy link
Contributor

brson commented Apr 13, 2016

Ah, I'm going to close this in favor of the aforementioned bug.

@brson brson closed this as completed Apr 13, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants