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.

Sign up for GitHub

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

Jump to bottom

Default toolchain not propagated to cygwin from msys #12

Closed
alexcrichton opened this issue Oct 9, 2015 · 4 comments
Closed

Default toolchain not propagated to cygwin from msys #12

alexcrichton opened this issue Oct 9, 2015 · 4 comments

Comments

@alexcrichton
Copy link
Member

I installed multirust in MSYS2 but then when running in a cygwin shell it reports that "no default toolchain is configured" (whereas in MSYS2 it works ok). Perhaps this is because $HOME is changing locations?
@Diggsey
Copy link
Contributor

Diggsey commented Oct 9, 2015

Yes, either define MULTIRUST_HOME to be somewhere consistent, or install multirust separately for cygwin.

This is because multirust-rs always installs for a single user (saves a lot of trouble with permissions, imagine if the overrides database was shared between users!) It's also how the python and ruby equivalents function.

Is there a reason why that is undesirable?

@alexcrichton
Copy link
Member Author

I would personally want to install multirust once and call it a day, having it "just work" everywhere I try to use it. For example when I open up cmd.exe I also don't have my toolchains installed there. I could install all the toolchains in all the shells, but it'd be nice if they all shared data!

@Diggsey
Copy link
Contributor

Diggsey commented Oct 10, 2015

OK, I'll change it to only look at the %USERPROFILE% variables.

TBH, I find it extremely questionable that rust's env::home_dir() function looks for %HOME% first on windows: the way I see it, that should only be the case when you are specifically compiling for a unix-like environment, such as msys/cygwin, which each have their own target triples.

When compiling for a normal windows target, it shouldn't even look at %HOME%.

@Diggsey
Copy link
Contributor

Diggsey commented Oct 11, 2015

This should be fixed now.

@Diggsey Diggsey closed this as completed Oct 11, 2015
@Diggsey Diggsey mentioned this issue Oct 12, 2015
Closed
@erde74 erde74 mentioned this issue Aug 15, 2016
Closed
djc added a commit that referenced this issue Jun 18, 2024
@djc
# This is a combination of 40 commits.
97dd0be 
# This is the 1st commit message:

Port cli_inst_interactive to CliTestContext

# The commit message #2 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #3 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #4 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #5 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #6 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #7 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #8 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #9 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #10 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #11 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #12 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #13 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #14 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #15 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #16 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #17 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #18 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #19 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #20 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #21 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #22 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #23 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #24 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #25 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #26 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #27 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #28 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #29 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #30 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #31 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #32 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #33 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #34 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #35 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #36 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #37 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #38 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #39 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #40 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext
djc added a commit that referenced this issue Jun 18, 2024
@djc
# This is a combination of 19 commits.
f9d90a3 
# This is the 1st commit message:

Port cli_misc to CliTestContext

# The commit message #2 will be skipped:

# fixup! Port cli_misc to CliTestContext

# The commit message #3 will be skipped:

# fixup! Port cli_misc to CliTestContext

# The commit message #4 will be skipped:

# fixup! Port cli_misc to CliTestContext

# The commit message #5 will be skipped:

# fixup! Port cli_misc to CliTestContext

# The commit message #6 will be skipped:

# fixup! Port cli_misc to CliTestContext

# The commit message #7 will be skipped:

# fixup! Port cli_misc to CliTestContext

# The commit message #8 will be skipped:

# fixup! Port cli_misc to CliTestContext

# The commit message #9 will be skipped:

# fixup! Port cli_misc to CliTestContext

# The commit message #10 will be skipped:

# fixup! Port cli_misc to CliTestContext

# The commit message #11 will be skipped:

# fixup! Port cli_misc to CliTestContext

# The commit message #12 will be skipped:

# fixup! Port cli_misc to CliTestContext

# The commit message #13 will be skipped:

# fixup! Port cli_misc to CliTestContext

# The commit message #14 will be skipped:

# fixup! Port cli_misc to CliTestContext

# The commit message #15 will be skipped:

# fixup! Port cli_misc to CliTestContext

# The commit message #16 will be skipped:

# fixup! Port cli_misc to CliTestContext

# The commit message #17 will be skipped:

# fixup! Port cli_misc to CliTestContext

# The commit message #18 will be skipped:

# fixup! Port cli_misc to CliTestContext

# The commit message #19 will be skipped:

# fixup! Port cli_misc to CliTestContext
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@alexcrichton @Diggsey