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

bundled fmt library can conflict with fmt installed in the same prefix #1845

Closed
nmm0 opened this issue Jun 7, 2022 · 0 comments · Fixed by #1847
Closed

bundled fmt library can conflict with fmt installed in the same prefix #1845

nmm0 opened this issue Jun 7, 2022 · 0 comments · Fixed by #1847
Assignees

Comments

@nmm0
Copy link
Collaborator

nmm0 commented Jun 7, 2022

Describe the bug
The bundled fmt library can overwrite or be overwritten by a different fmt version that is not compatible if installed to the same prefix. This kind of situation is a bit rare but shows up in spack environments and some docker installs.

The fmt library should be prefixed to make it unique.

@nmm0 nmm0 added the type: bug label Jun 7, 2022
@nmm0 nmm0 self-assigned this Jun 7, 2022
@nmm0 nmm0 closed this as completed in #1847 Jun 9, 2022
nmm0 added a commit that referenced this issue Jun 9, 2022
…can-conflict-with-fmt-installed-in-the-same-prefix

#1845: bundled fmt library can conflict with fmt installed in the same prefix
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant