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

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

Conversation

nmm0
Copy link
Collaborator

@nmm0 nmm0 commented Jun 8, 2022

This PR renames libfmt{d}.a to libfmt-vt{d}.a in order to prevent conflicts with fmt installed in the same root. Additionally, it renames the include directory from fmt to fmt-vt.

Closes #1845

@nmm0 nmm0 linked an issue Jun 8, 2022 that may be closed by this pull request
@nmm0
Copy link
Collaborator Author

nmm0 commented Jun 8, 2022

We don't have a test for this but I have verified that this works in a spack install environment with fmt installed additionally as a separate package.

@nmm0 nmm0 requested review from lifflander, cz4rs and PhilMiller June 8, 2022 18:25
@github-actions
Copy link

github-actions bot commented Jun 8, 2022

Pipelines results

PR tests (gcc-5, ubuntu, mpich)

Build for 164ba7c

Compilation - successful

Testing - passed

Build log


PR tests (clang-3.9, ubuntu, mpich)

Build for 164ba7c

Compilation - successful

Testing - passed

Build log


PR tests (gcc-10, ubuntu, openmpi, no LB)

Build for 164ba7c

Compilation - successful

Testing - passed

Build log


PR tests (clang-5.0, ubuntu, mpich)

Build for 164ba7c

Compilation - successful

Testing - passed

Build log


PR tests (gcc-9, ubuntu, mpich, zoltan)

Build for 164ba7c

Compilation - successful

Testing - passed

Build log


PR tests (gcc-6, ubuntu, mpich)

Build for 164ba7c

Compilation - successful

Testing - passed

Build log


PR tests (gcc-7, ubuntu, mpich, trace runtime, LB)

Build for 164ba7c

Compilation - successful

Testing - passed

Build log


PR tests (clang-9, ubuntu, mpich)

Build for 164ba7c

Compilation - successful

Testing - passed

Build log


PR tests (nvidia cuda 10.1, ubuntu, mpich)

Build for 164ba7c

Compilation - successful

Testing - passed

Build log


PR tests (clang-13, alpine, mpich)

Build for 164ba7c

Compilation - successful

Testing - passed

Build log


PR tests (nvidia cuda 11.0, ubuntu, mpich)

Build for 164ba7c

Compilation - successful

Testing - passed

Build log


PR tests (clang-11, ubuntu, mpich)

Build for 164ba7c

Compilation - successful

Testing - passed

Build log


PR tests (intel icpx, ubuntu, mpich)

Build for 164ba7c

Compilation - successful

Testing - passed

Build log


PR tests (clang-13, ubuntu, mpich)

Build for 164ba7c

Compilation - successful

Testing - passed

Build log


PR tests (clang-12, ubuntu, mpich)

Build for 164ba7c

Compilation - successful

Testing - passed

Build log


PR tests (clang-14, ubuntu, mpich)

Build for 164ba7c

Compilation - successful

Testing - passed

Build log


PR tests (gcc-8, ubuntu, mpich, address sanitizer)

Build for 164ba7c

Compilation - successful

Testing - passed

Build log


PR tests (gcc-11, ubuntu, mpich)

Build for 164ba7c

Compilation - successful

Testing - passed

Build log


PR tests (clang-10, ubuntu, mpich)

Build for 164ba7c

Compilation - successful

Testing - passed

Build log


PR tests (gcc-12, ubuntu, mpich)

Build for 164ba7c

Compilation - successful

Testing - passed

Build log


PR tests (intel icpc, ubuntu, mpich)

Build for 164ba7c

Compilation - successful

Testing - passed

Build log


@@ -14,6 +14,7 @@ set(FMT_SOURCES src/format.cc)

add_library(fmt ${FMT_SOURCES} ${FMT_HEADERS})
Copy link
Member

Choose a reason for hiding this comment

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

Should we change the CMake name as well? If a downstream code ends up picking this up, it'll be a bit confusing

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

hmm yeah, there might be a problem with duplicate targets if they happen to also be including fmt as a subdirectory

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Overall I'd be more in favor of a more permanent solution which would be to optionally force vt to use external versions of these libraries. That would be ideal for the spack case. I'd like to get this merged now however because it is causing some breakages in some internal CI processes

Copy link
Contributor

@cz4rs cz4rs left a comment

Choose a reason for hiding this comment

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

Looks good for me as is.
Possibly another issue can be opened for the "more permanent solution" as discussed?

@nmm0
Copy link
Collaborator Author

nmm0 commented Jun 9, 2022

Looks good for me as is. Possibly another issue can be opened for the "more permanent solution" as discussed?

Added #1848

@nmm0 nmm0 merged commit a9753fe into develop Jun 9, 2022
@nmm0 nmm0 deleted the 1845-bundled-fmt-library-can-conflict-with-fmt-installed-in-the-same-prefix branch June 9, 2022 17:03
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.

bundled fmt library can conflict with fmt installed in the same prefix
3 participants