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

Failed to run on Windows 11 #203

Open
1 task done
burdiyan opened this issue Oct 13, 2023 · 4 comments
Open
1 task done

Failed to run on Windows 11 #203

burdiyan opened this issue Oct 13, 2023 · 4 comments
Labels

Comments

@burdiyan
Copy link

Solution to issue cannot be found in the documentation.

  • I checked the documentation.

Issue

After creating an environment with this conda package, and activating it, any call to go (e.g. go version) fails with the following error:

go: cannot find GOROOT directory: 'go' binary is trimmed and GOROOT is not set

Interestingly doing the same via conda run works fine.

I'm using PowerShell 7 and miniconda3.

Installed packages

# Name                    Version                   Build  Channel
_go_select                2.3.0                       cgo    conda-forge
go                        1.21.3               hf68ea12_0    conda-forge
m2w64-gcc-libgfortran     5.3.0                         6    conda-forge
m2w64-gcc-libs            5.3.0                         7    conda-forge
m2w64-gcc-libs-core       5.3.0                         7    conda-forge
m2w64-gmp                 6.1.0                         2    conda-forge
m2w64-libwinpthread-git   5.0.0.4634.697f757               2    conda-forge
msys2-conda-epoch         20160418                      1    conda-forge

Environment info

active environment : mintter-dev
    active env location : C:\Users\horac\miniconda3\envs\mintter-dev
            shell level : 1
       user config file : C:\Users\horac\.condarc
 populated config files : C:\Users\horac\.condarc
          conda version : 23.5.2
    conda-build version : not installed
         python version : 3.11.4.final.0
       virtual packages : __archspec=1=x86_64
                          __win=0=0
       base environment : C:\Users\horac\miniconda3  (writable)
      conda av data dir : C:\Users\horac\miniconda3\etc\conda
  conda av metadata url : None
           channel URLs : https://repo.anaconda.com/pkgs/main/win-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/r/win-64
                          https://repo.anaconda.com/pkgs/r/noarch
                          https://repo.anaconda.com/pkgs/msys2/win-64
                          https://repo.anaconda.com/pkgs/msys2/noarch
          package cache : C:\Users\horac\miniconda3\pkgs
                          C:\Users\horac\.conda\pkgs
                          C:\Users\horac\AppData\Local\conda\conda\pkgs
       envs directories : C:\Users\horac\miniconda3\envs
                          C:\Users\horac\.conda\envs
                          C:\Users\horac\AppData\Local\conda\conda\envs
               platform : win-64
             user-agent : conda/23.5.2 requests/2.29.0 CPython/3.11.4 Windows/10 Windows/10.0.22621 solver/libmamba conda-libmamba-solver/23.5.0 libmambapy/1.4.1
          administrator : False
             netrc file : None
           offline mode : False
@burdiyan burdiyan added the bug label Oct 13, 2023
@xhochy
Copy link
Member

xhochy commented Oct 22, 2023

Do you first activate the environment and then run go or is this error only happening without activation?

@burdiyan
Copy link
Author

@xhochy This happens after activating the environment, as I mentioned in the initial message:

After creating an environment with this conda package, and activating it.

I suspect the problem is that I'm doing it through PowerShell, but the activation script that sets the GOROOT environment variable is written for CMD according to this package's recipe. So, maybe it just doesn't work under PowerShell?

@xhochy
Copy link
Member

xhochy commented Oct 29, 2023

This could be the issue. But I have seen very packages actually having activation scripts for powershell. Thus, I had the belief that powershell users would get the activation through CMD. Still, I'm confused that this error is popping up as we don't set GOROOT in any activation script.

@burdiyan
Copy link
Author

burdiyan commented Nov 7, 2023

I could swear I've seen something related to GOROOT in the activation script, but I can't see now :(

Regardless, the issue is still there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants