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.

Sign up for GitHub

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

Jump to bottom

phasar installs files from googletest, nlohmann json #566

Open
yurivict opened this issue Jan 15, 2023 · 3 comments
Open

phasar installs files from googletest, nlohmann json #566

yurivict opened this issue Jan 15, 2023 · 3 comments
Labels
done-elsewhere This is taken care of in a different PR

Comments

@yurivict
Copy link

yurivict commented Jan 15, 2023 •
edited 

===>   Registering installation for phasar-1222
Installing phasar-1222...
pkg-static: phasar-1222 conflicts with googletest-1.12.1 (installs files into the same place).  Problematic file: /usr/local/include/gtest/gtest-death-test.h
*** Error code 1

===>   Registering installation for phasar-1222
Installing phasar-1222...
pkg-static: phasar-1222 conflicts with nlohmann-json-3.11.2 (installs files into the same place).  Problematic file: /usr/local/include/nlohmann/json.hpp
*** Error code 1

Version: 1222
@yurivict yurivict changed the title phasar installs files from googletest phasar installs files from googletest, nlohmann json Jan 15, 2023
@fabianbs96
Copy link
Member

PhASAR installs these dependencies, because it needs them to compile and run. We are aware that version conflicts are a problem and we are currently completely overhauling our dependency management. See #516.

@MMory MMory added the done-elsewhere This is taken care of in a different PR label Mar 2, 2023
@yurivict
Copy link
Author

yurivict commented Mar 4, 2024

@fabianbs96

Any chance to fix this?
All distros must have the same problem with conflict between nlohmann json versions.
This prevents porting efforts or makes them more difficult.

@fabianbs96 fabianbs96 mentioned this issue Mar 4, 2024
Merged
@fabianbs96
Copy link
Member

Hi @yurivict,
I understand that this is an issue, however, fixing this properly is not straightforward. Can you check whether #707 fixes your issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
done-elsewhere This is taken care of in a different PR
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@yurivict @MMory @fabianbs96