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

Do we still need this mutex? #6

Open
h-vetinari opened this issue Dec 11, 2024 · 0 comments · May be fixed by conda-forge/_openmp_mutex-feedstock#12
Open

Do we still need this mutex? #6

h-vetinari opened this issue Dec 11, 2024 · 0 comments · May be fixed by conda-forge/_openmp_mutex-feedstock#12

Comments

@h-vetinari
Copy link
Member

h-vetinari commented Dec 11, 2024

Since conda-forge/ctng-compilers-feedstock#148, conda-forge now switched back from the old libgcc-ng name to the even older original libgcc (AFAIU). This was before my time, so I don't know the details, but the following stood out to me

summary: 'Mutex for libgcc and libgcc-ng'

It sounds like it wasn't possible then to mix libgcc and libgcc-ng, but looking at

libgcc_mutex_build_string:
- main
- free
- conda_forge

it actually seems to be more of a inter-channel question, rather than something within conda-forge itself.

As such, I think we can remove this package from being depended on in our compilers etc.

Thoughts @conda-forge/_libgcc_mutex ?

Edit: Hm, github doesn't seem to want to ping the feedstock here... CC @beckermr @isuruf

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 a pull request may close this issue.

1 participant