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

Version 1.76.0 #6

Merged
merged 13 commits into from
Mar 20, 2024
Merged

Version 1.76.0 #6

merged 13 commits into from
Mar 20, 2024

Conversation

SC426
Copy link

@SC426 SC426 commented Mar 13, 2024

rust-activation 1.76.0

Destination channel: defaults

Links

Explanation of changes:

  • Update version and sha256
  • Linter fixes
  • Update tests
  • Change clang deployment target version for osx-64 to 10.12

Copy link

@cbouss cbouss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link

@skupr-anaconda skupr-anaconda left a 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

@danpetry
Copy link

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)

@cbouss
Copy link

cbouss commented Mar 14, 2024

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

It's for rust-gnu only, which is the rust compiler on windows using the msys2 compiler as a backend.
The regular rust package for windows uses msvc.

@danpetry
Copy link

danpetry commented Mar 14, 2024

AFAIU, the activation packages are called <compiler_name>_<platform> and handles the {{ compiler('<compiler_name>') }} jinja function where in cbc.yaml you have

c_compiler:
   - <compiler_name>

And <platform> is defined somewhere else for each platform (in conda maybe?)

And they often set environment variables or config scripts as well as installing the compiler itself

@ryanskeith
Copy link

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.

@anaconda-pkg-build
Copy link

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 =====

  • clone/recipe/meta.yaml:0: output_script_name_default: output "rust_linux-aarch64": Output should not use default script names build.sh/bld.bat.
  • clone/recipe/meta.yaml:0: output_script_name_default: output "rust_osx-arm64": Output should not use default script names build.sh/bld.bat.
  • clone/recipe/meta.yaml:0: output_script_name_default: output "rust_linux-s390x": Output should not use default script names build.sh/bld.bat.
  • clone/recipe/meta.yaml:0: output_script_name_default: output "rust_osx-64": Output should not use default script names build.sh/bld.bat.
  • clone/recipe/meta.yaml:0: output_script_name_default: output "rust_linux-64": Output should not use default script names build.sh/bld.bat.
  • clone/recipe/meta.yaml:0: output_script_name_default: output "rust_linux-ppc64le": Output should not use default script names build.sh/bld.bat.
    ===== Final Report: =====
    6 Errors and 0 Warnings were found

@anaconda-pkg-build
Copy link

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 =====

  • clone/recipe/meta.yaml:0: output_script_name_default: output "rust_linux-64": Output should not use default script names build.sh/bld.bat.
  • clone/recipe/meta.yaml:0: output_script_name_default: output "rust_linux-aarch64": Output should not use default script names build.sh/bld.bat.
  • clone/recipe/meta.yaml:0: output_script_name_default: output "rust_osx-64": Output should not use default script names build.sh/bld.bat.
  • clone/recipe/meta.yaml:0: output_script_name_default: output "rust_linux-ppc64le": Output should not use default script names build.sh/bld.bat.
  • clone/recipe/meta.yaml:0: output_script_name_default: output "rust_osx-arm64": Output should not use default script names build.sh/bld.bat.
  • clone/recipe/meta.yaml:0: output_script_name_default: output "rust_linux-s390x": Output should not use default script names build.sh/bld.bat.
    ===== Final Report: =====
    6 Errors and 0 Warnings were found

@SC426 SC426 merged commit e8ea4e3 into master Mar 20, 2024
1 of 3 checks passed
@SC426 SC426 deleted the v1.76.0 branch March 20, 2024 14:40
@anaconda-pkg-build
Copy link

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 =====

  • clone/recipe/meta.yaml:0: output_script_name_default: output "rust_osx-arm64": Output should not use default script names build.sh/bld.bat.
  • clone/recipe/meta.yaml:0: output_script_name_default: output "rust_linux-aarch64": Output should not use default script names build.sh/bld.bat.
  • clone/recipe/meta.yaml:0: output_script_name_default: output "rust_linux-ppc64le": Output should not use default script names build.sh/bld.bat.
  • clone/recipe/meta.yaml:0: output_script_name_default: output "rust_linux-64": Output should not use default script names build.sh/bld.bat.
  • clone/recipe/meta.yaml:0: output_script_name_default: output "rust_osx-64": Output should not use default script names build.sh/bld.bat.
  • clone/recipe/meta.yaml:0: output_script_name_default: output "rust_linux-s390x": Output should not use default script names build.sh/bld.bat.
    ===== Final Report: =====
    6 Errors and 0 Warnings were found

@anaconda-pkg-build
Copy link

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 =====

  • clone/recipe/meta.yaml:0: output_script_name_default: output "rust_linux-aarch64": Output should not use default script names build.sh/bld.bat.
  • clone/recipe/meta.yaml:0: output_script_name_default: output "rust_osx-64": Output should not use default script names build.sh/bld.bat.
  • clone/recipe/meta.yaml:0: output_script_name_default: output "rust_linux-ppc64le": Output should not use default script names build.sh/bld.bat.
  • clone/recipe/meta.yaml:0: output_script_name_default: output "rust_linux-64": Output should not use default script names build.sh/bld.bat.
  • clone/recipe/meta.yaml:0: output_script_name_default: output "rust_linux-s390x": Output should not use default script names build.sh/bld.bat.
  • clone/recipe/meta.yaml:0: output_script_name_default: output "rust_osx-arm64": Output should not use default script names build.sh/bld.bat.
    ===== Final Report: =====
    6 Errors and 0 Warnings were found

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

Successfully merging this pull request may close these issues.

7 participants