-
Notifications
You must be signed in to change notification settings - Fork 0
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
Version 1.76.0 #6
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not typical for m2w64-toolchain # [win]
to be in the run
section. Because it's a build tool. It's dependencies are:
m2w64-binutils, m2w64-crt-git, m2w64-gcc, m2w64-gcc-ada, m2w64-gcc-fortran, m2w64-gcc-libgfortran, m2w64-gcc-libs, m2w64-gcc-objc, m2w64-headers-git, m2w64-libmangle-git, m2w64-libwinpthread-git, m2w64-make, m2w64-pkg-config, m2w64-tools-git, m2w64-winpthreads-git, msys2-conda-epoch >=20160418
But I'm not familiar with activation scripts
I'm not either, but I think it means that if the activation packages are used in a build environment, they pull in their compilers and other required tools to the build environment too. In other words, the activation packages need the toolchain to run (in a build environment) |
It's for rust-gnu only, which is the rust compiler on windows using the msys2 compiler as a backend. |
AFAIU, the activation packages are called
And And they often set environment variables or config scripts as well as installing the compiler itself |
I know it may be bothersome but there is a fundamental difference in how we do rust activations versus conda forge. On everything but windows, we create a file but we should just make use of environment variables. |
Linter check found the following problems:ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_6354cpztoo/clone` failed. (See above for error) The following problems have been found:===== ERRORS =====
|
Linter check found the following problems:ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_b26pemeehj/clone` failed. (See above for error) The following problems have been found:===== ERRORS =====
|
…feedstock into v1.76.0
Linter check found the following problems:ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_340yr43q53/clone` failed. (See above for error) The following problems have been found:===== ERRORS =====
|
Linter check found the following problems:ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_9bdqo9t0r5/clone` failed. (See above for error) The following problems have been found:===== ERRORS =====
|
rust-activation 1.76.0
Destination channel: defaults
Links
Explanation of changes:
sha256
osx-64
to 10.12