-
Notifications
You must be signed in to change notification settings - Fork 65
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
Windows: 'update stable' downloads wrong architecture #315
Comments
Here is the same problem with
|
It happened to me the other day too on Windows, I think when trying to upgrade to 1.6.12. Deleted everything choosenim and nimble related and reinstalled, and got x64. |
Hey @daniel-j
I tried that, no changes. NEW OBSERVATION:
C:\WINDOWS\system32>choosenim update devel
Updating devel
Info: Using the 'GITHUB_TOKEN' environment variable for GitHub API Token.
Downloading Nim latest-devel from GitHub
[##################################################] 100.0% 0kb/s
Extracting windows_x32.zip
Setting up git repository
Building Nim #devel
Compiler: Already built
Updated to #devel
Info: Version #devel already selected
C:\Users\matic> choosenim update devel
Updating devel
Info: Using the 'GITHUB_TOKEN' environment variable for GitHub API Token.
Downloading Nim latest-devel from GitHub
[##################################################] 100.0% 0kb/s
Extracting windows_x64.zip
Setting up git repository
Building Nim #devel
Compiler: Already built
Updated to #devel
Info: Version #devel already selected Where is the heuristic to detect the architecture on Windows in the code located? |
Hi,
My specs: Windows 10 x64,
choosenim
installed manually.I had installed
1.6.8
previously a couple of months ago withchoosenim update stable
and it worked without problems.Tried the same with
1.6.10
a couple of days ago, but it downloaded thex86
version. Here is the forum post I posted the problem on: https://forum.nim-lang.org/t/9643. I removed1.6.10
and reinstalled it at least twice with:... but each time it downloaded the wrong architecture.
But after a day, maybe because of a reboot or something else (I honestly don't know what else could it be), it worked?
Any ideas what went wrong here?
The text was updated successfully, but these errors were encountered: