add clang 19.1

[h-vetinari]

No description provided.

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

[h-vetinari]

This PR (as of 454ff7f) needs conda-forge/clangdev-feedstock@d21fa80 (from conda-forge/clangdev-feedstock#322), plus backports of that commit to 17.x & 18.x

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found some lint.

Here's what I've got...

For recipe/meta.yaml:

• Recipe maintainer "isuruf" does not exist
• Recipe maintainer "beckermr" does not exist

[h-vetinari]

• Recipe maintainer "beckermr" does not exist

@beckermr, the linter seems to believe you have ceased existing 🤭

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

[h-vetinari]

This should now be ready, PTAL @conda-forge/ctng-compiler-activation

With conda-forge/clangdev-feedstock@5751f79 after discussion in conda-forge/clangdev-feedstock#322, we now mirror clang_impl_{{ target }} also on the linux side, but on this feedstock.

I've tried matching the structure of the scripts with the clang-compiler-activation, and I'll also rename the scripts on the clang-activation to match the script naming here, so ultimately we converge to a recognizably similar setup despite being spread across different feedstocks.

[h-vetinari]

Gentle ping @isuruf

[isuruf]

There's a conda-build bug and this needs a rerender with an older version to make sure the .ci_support are not duplicated.

[h-vetinari]

These are unnecessary with the sysroot update

Just for my understanding: Does clang pick up the .cfg's even if only part of the binary path matches? Before we had

bin/x86_64-conda-linux-gnu-clang.cfg
bin/x86_64-conda-linux-gnu-clang++.cfg
bin/x86_64-conda-linux-gnu-clang-cpp.cfg

after conda-forge/linux-sysroot-feedstock@c53a630 we now only have

bin/x86_64-conda-linux-gnu.cfg

[isuruf]

The rules for the names are in https://clang.llvm.org/docs/UsersManual.html#configuration-files. It searches for <triple>-<driver>.cfg and <triple>.cfg.

[h-vetinari]

Thanks, that makes sense! Anything else to do here?

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found some lint.

Here's what I've got...

For recipe/meta.yaml:

• pin_compatible should be used instead of pin_subpackage for clang_impllinux-64 because it is not a known output of this recipe: ['gcc_linux-64', 'clang_impl_linux-64', 'clang_linux-64', 'gxx_linux-64', 'clangxx_impl_linux-64', 'clangxx_linux-64', 'gfortran_linux-64', 'gcc_bootstrap_linux-64', 'ctng-compiler-activation'].

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

[h-vetinari]

Are we good here now @isuruf? :)

[h-vetinari]

Ping @isuruf

[h-vetinari]

Ping @isuruf

The issue with the conda-build bug has been addressed in this PR (and ideally a fix may even make it into CB 24.11 🤞)

[h-vetinari]

@isuruf, this has been ready for >2 weeks and is just missing a merge. Given your preference of me not joining as a maintainer, please help me finish this. The alternative is that I bring up shared compiler maintenance (i.e. me joining the GCC & VC feedstocks) in core, up to a vote if necessary.

[isuruf]

Thanks