clangdev v13.0.0 (redux)

[h-vetinari]

Closes #157

Also add myself to maintainers as discussed here.

[conda-forge-linter]

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) and found it was in an excellent condition.

[h-vetinari]

@isuruf, this is needed by build.sh before any of the outputs.

My question is: do we also need to add zlib to all of the outputs individually?

[h-vetinari]

Currently following a minimal approach to add this only where needed (even though that takes a couple iterations).

[h-vetinari]

OK, finally zlib added in enough places. For the python-bindings failure, I have very little to go on, though.

The upstream readme mentions setting CLANG_LIBRARY_PATH=$(llvm-config --libdir) (though that's not a recent change, i.e. no change from LLVM 12). Should we set this somewhere in the recipe?

[h-vetinari]

Whaaa...? The build passed before on OSX, and now, with linux-only changes, it fails as well upon import.

The only candidate I can think of is that this is due to the python 3.10 builds that were merged today (which get pulled in due to noarch: python). @isuruf

[isuruf]

Yes. See conda/conda#10969

[h-vetinari]

@isuruf, there's still something not working out with 3.10 (on osx).

With python 3.10:

+ python -m unittest discover -v
test_access_specifiers (tests.cindex.test_access_specifiers.TestAccessSpecifiers)
Ensure that C++ access specifiers are available on cursors ... /Users/runner/miniforge3/conda-bld/clang_packages_1634249809314/test_tmp/run_test.sh: line 8: 37957 Abort trap: 6           python -m unittest discover -v
Tests failed for python-clang-13.0.0-default_hccd1708_0.tar.bz2 - moving package to /Users/runner/miniforge3/conda-bld/broken

With python 3.9 it passes (see CI of last two commits).

[h-vetinari]

Ping @isuruf, any idea why 3.10 is failing here, resp. would you be fine to merge the PR with python <3.9 for now?

[h-vetinari]

Ping @isuruf :)

[isuruf]

Can you enable artifacts on azure and revert to using 3.10 so we can debug this?

[h-vetinari]

Can you enable artifacts on azure and revert to using 3.10 so we can debug this?

Done, failure on OSX remains. I don't have an Apple machine to test this though.

[h-vetinari]

Ping @isuruf; artefacts are now available.

[h-vetinari]

@conda-forge/clangdev

After the libffi-issues got fixed on the python-feedstock, this is now green! 🥳

The only thing that stood out to me from the logs was the following ClobberWarning that we might want to have a look at (possibly in a separate PR to unblock LLVM 13)?

ClobberWarning: This transaction has incompatible packages due to a shared path.
  packages: conda-forge/osx-64::clang_bootstrap_osx-64-12.0.1-h3b6de16_2, conda-forge/osx-64::libcxx-12.0.1-habf9029_0
  path: 'include/c++/v1/bitset'